It simply means, for the tests that it completed, it did not find any issues. It is also important to note that just because the data integrity returns that there were no problems detected with your data that does not mean you do not have data base damage. If you are unsure if it is working or not, open the Windows Task Manager and on the process tab find the QuickBooks program file (mine is QBW32.exe) and confirm the memory usage is changing. This seems to be a very common occurrence and if you just wait, it will probably be ok. Do not be quick to cancel or restart the computer. ![]() It is not uncommon for the top of the progress bar box to state that the software is not responding, especially for larger files. There will be a progress bar to show that the process is working. To start the analysis, choose File > Utilities > Verify Data. It is recommended that the verify data be done in single user mode for the most complete analysis. We have been seeing much more file damage recently and the sooner you catch the issue, the more likely it is that the rebuild functionality will resolve the issue before you end up needing Intuit’s Data Services team. Others get in the habit of doing it last thing each Friday for the consistency. For our clients, we encourage them to add it to their month end procedures and complete the process when working on the bank reconciliation. Our rule of thumb is immediately anytime there is an issue, such as getting kicked out of QuickBooks, but at least monthly. This is something that should be done on a regular basis. This is a critical component of QuickBooks data file maintenance that should not wait for a formal assessment of the file. One of the best ways to quickly and easily determine if there is an underlying database issue is the process of verifying data To determine the file and size, number of data base file fragments, and number of versions used on the file, press F2 (or Ctrl+1) and in the product information screen you will see all of this and more: ![]() I cannot say that this is why we are seeing more data integrity issues, but it seems like a logical contributing factor. That is a lot of data base manipulation in addition to the strain of all the transactional data entry. We have seen instances where a single file has been upgraded from version to version and release to release in excess of 35 times. All of the version upgrades (through feature enhancements and data base changes) can take their toll on the file. One issue that is important to note is that QuickBooks has been the small business accounting software of choice for many years, and because of this, clients have often been using the same data file for that entire time. No matter what works the best for you, regular analysis is important to discover issues, hopefully before they become so prevalent that you have a big clean up job on your hands. Others use our Small Business Diagnostic Tool: QuickBooks Edition ( ) to provide a consistent approach. Others have a checklist that they use in Excel or Word as part of their procedures. ![]() Some people take a Balance Sheet approach as the first step: Go through each account and make sure that it looks accurate, proper procedures are being used, detail reports look reasonable, etc. In my opinion, the first step is to take a step back and really look at the health of the file. While we take the approach that each situation is unique and there is not one size that fits all situations, there are a few data health issues we have been seeing more frequently that bear mention. The time of the year is going to be quickly upon us when Intuit traditionally releases a new version of the software, and clients begin asking questions not only about upgrading but also about new files.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |