The program could not create your data because it could not find the database
Sage 50 is telling you it cannot locate or open the database behind your company data, not that your data is gone.
You have just seen this message:
The program could not create your data because it could not find the database.
Despite the wording, Sage 50 is not usually telling you that your data was destroyed. It is telling you that it cannot find or attach to the database that holds your company data. The program and the data are separate things. Sage 50 opens a company file, and behind that file sits a database engine. When the engine cannot be reached, or the data files it points to are missing or unreadable, you get this message instead of a company window.
Where does this message come from?
It typically appears when Sage 50 tries to open or create a company and the database layer fails to respond. Common triggers include a data path that has moved, a mapped network drive that is no longer connected, a database service that did not start, or a company folder whose files were renamed, copied, or partially restored. It can also appear after an interrupted update or a restore from backup that did not include every file the database needs.
Check the simple things first
Close Sage 50 completely and reopen it. If the data lives on a network share, confirm the share is reachable and that the mapped drive letter has not changed. If you were restoring a backup, restore it again to a fresh folder rather than over an existing one. Make sure you are logged in with sufficient rights to the folder holding the data. These steps cost nothing and resolve a fair share of cases.
Do not keep retrying over a damaged folder
If the folder holding your company data was copied while Sage 50 was running, or a restore was interrupted, some of the database files may be incomplete. Repeated attempts to open it will not fix that. Stop, make a copy of the entire company data folder while it is in its current state, and work only on the copy. That preserves your best recovery point.
When the data itself is the problem
If the path is correct and the database still will not attach, the data files themselves are likely damaged. This is the point where professional repair is the safe answer. Our engineers work on damaged Sage 50, Peachtree, and Simply Accounting databases regularly, and we can usually tell quickly whether the data is recoverable. See our Sage 50 / Simply Accounting database repair service for what that involves.
If you were converting or moving the data
This message also shows up during a conversion or a move to a new machine, when the target setup is incomplete. If your goal is to get the data into QuickBooks, that can often be done directly from the existing files even when Sage 50 itself will not open them. Our Sage 50 to QuickBooks conversion service covers that path, and we have a separate page for Simply Accounting (Sage 50 Canada) conversions.
A useful next step
Before anything else, copy the whole company data folder somewhere safe. Then send us the copy for a free evaluation. We will assess what is recoverable and quote you before any work starts, so you know exactly where you stand.