Overview
QQube uses SAP SQL Anywhere database technology, the same database platform used by QuickBooks. It is designed for high performance and strict data integrity.
However, the QQube database can become incomplete or inconsistent after interrupted synchronization, QuickBooks file corruption, QuickBooks list changes, or certain preference and data changes.
A complete reload requires both options
The only way to clear the QQube database and reload it from scratch is to select both Run All and Clear all data on synch start in the QQube Configuration Tool.
A complete reload can take considerable time for large QuickBooks company files because data extraction is limited by the Intuit Software Development Kit. Data accuracy must take priority over reload time.
QQube Version 10 can reduce the amount of historical data reloaded by using a selected beginning period where the applicable data model supports it.
When a Complete Clear and Reload Is Required
The following events require a complete clear and reload. A normal synchronization is not sufficient.
QuickBooks Changes
| Change | When a Reload Is Required |
|---|---|
| QuickBooks year upgrade | Required when upgrading from one QuickBooks year to another, such as 2023 to 2024. A maintenance release within the same year, such as Release 3 to Release 4, does not require a reload. |
| QuickBooks company file rebuild | Required after using the QuickBooks Rebuild Data utility. |
| QuickBooks list merge | Required after merging accounts, items, or customers. |
| Custom field name change | Required whenever an existing QuickBooks custom field is renamed. |
| QuickBooks data corruption | Required after corruption is identified or repaired. |
Synchronization Interruptions
| Interruption | Example or Condition |
|---|---|
| Manual synchronization abort | The synchronization is manually stopped from the QQube Configuration Tool. |
| QuickBooks crash | QuickBooks closes unexpectedly while QQube is synchronizing. |
| Synch user logged off | The Windows user running the synchronization is logged off before the process completes. |
| Second QuickBooks instance | Another QuickBooks session is opened under the same Windows user during synchronization. |
| Backup interference | A backup process affects QuickBooks while QQube is synchronizing. |
| Third-party application conflict | Another application connects to QuickBooks under the same Windows user while QQube is synchronizing. |
| Other abnormal interruption | Any unexpected event prevents the synchronization from completing normally. |
Data Accuracy and Support Requirements
| Situation | Required Action |
|---|---|
| Previously accurate data becomes inconsistent | Perform a complete clear and reload before continuing with additional troubleshooting. |
| CLEARIFY Engineering requests a reload | Perform the complete clear and reload exactly as directed. |
Why a normal synchronization is not enough
A later successful synchronization does not repair data left incomplete by an earlier interruption or structural QuickBooks change. The existing QQube database must be cleared before all required data is extracted again.
Expected Result
QQube removes the existing synchronized data and rebuilds the database from the QuickBooks company file using the current configuration, list structure, preferences, and selected date ranges.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article