Sage Conversion Questions
Sage Conversion Questions
Short, direct answers to the questions we're asked most about Sage to QuickBooks conversions and Sage 50 Quantum downgrades.
An error has occurred during the save of the report" in Sage 50
Sage 50 could not write a report to disk, usually because of a save-location problem or a damaged company file.
Sage 50A read-only company only can be restored as a read-only company" in Sage 50
Sage 50 is telling you the backup you are restoring was marked read-only, and it will stay read-only after restore.
ConversionYour application cannot access QuickBooks until the user dismisses the dialog box
This message means QuickBooks is waiting on a popup window that must be closed before another program can connect to your company file.
ConversionWith QB2006, this error occurred" opening a file made in a beta version
QuickBooks refuses to open the file because a released program cannot read one saved by a newer beta build.
Sage 50Will Sage 50 inventory assemblies and sub-assemblies convert to QuickBooks?
Yes, assemblies can map to QuickBooks inventory assembly items, but the result depends on your file and needs checking after conversion.
ConversionWhat should I do with open Sage 50 purchase orders for discontinued items?
Close or clean up stale open purchase orders in Sage 50 before converting, so the QuickBooks file does not inherit dead commitments.
ConversionUnable to log into this QuickBooks company file automatically" explained
This message means an outside application tried to open your company file silently and QuickBooks refused, so a login step is needed.
Sage 50Unable to lock the necessary information" Sage 50 error explained
This Sage 50 message means another user, session, or process is holding the company data file open, so your request cannot proceed.
Sage 50The record you are trying to access is currently in use" in Sage 50
This Sage 50 message means another user, session, or stale lock is holding the record, not that your data is gone.
Sage 50The program could not open the test file in the company directory" Sage 50 fix
Sage 50 is failing a read/write check on your company folder, usually a permissions or file-access problem rather than a broken company file.
Sage 50The program could not create a test file in the company's directory" Sage 50 error
Sage 50 cannot write to the folder holding your company data, usually a permissions or network problem, not file damage.
Sage 50The next primary id is not found for the specified database table" in Sage 50
Sage 50 cannot find the next ID number for a table, which usually means the company database is damaged internally.