Topic
Sage 50
Sage 50 (US Peachtree and Canadian Simply Accounting) conversions, editions, and downgrades. 36 guides and 425 answers on this topic.
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.
AnswerSage 50An error occurred while clearing transaction lookup data" in Sage 50
Sage 50 failed while purging its internal transaction lookup tables, usually a sign of database damage or a locked file.
AnswerSage 50An unexpected error occurred while copying your report to Microsoft Excel
Sage 50 could not hand your report over to Excel, usually because of a connection or Excel setup problem, not data loss.
AnswerConversionCan I keep using Sage 50 while the conversion to QuickBooks is running?
Yes, but pick a freeze date first. Keep working in Sage up to that date, then enter new activity only in QuickBooks after cutover.
AnswerSage 50Could not create or write to temporary file for XML Append Operation" Sage 50 error
Sage 50 cannot create the temporary working file it needs during an XML export or conversion, usually a permissions or disk problem.
AnswerSage 50Error during write of Form File" in Sage 50: what it means
Sage 50 could not save its form file. The disk-space wording is often a guess; the real cause is usually damage or a permissions problem.
AnswerSage 50Reverse transaction cannot be in the last period of the second year" in Sage 50
Sage 50 blocks a reversing entry dated into the second fiscal year; the date and the open-year rules are the real problem.
AnswerSage 50Sage 50 cannot find a required file or it has been corrupted
This message means Sage 50 could not open a file it needs, usually a damaged company data file rather than a missing program component.
AnswerSage 50Sage 50 message: "This invoice has payments applied to it and cannot be voided
Sage 50 refuses to void an invoice because customer payments are linked to it; unlink or reverse them first, or adjust differently.
AnswerSage 50The newly inserted object could not be assigned a key by the data source" in Sage 50
Sage 50 cannot generate an internal ID for the record you just saved, which usually points to database damage.
AnswerSage 50This invoice voids another invoice and cannot be voided" in Sage 50
Sage 50 refuses to void an invoice because that invoice is itself the voiding entry for another invoice.
AnswerSage 50Transactions posted to the general ledger in a closed year cannot be accessed or edited
Sage 50 is telling you the transaction lives in a fiscal year you already closed, so it is locked against changes.