Unable to set the file includes headers flag" in Sage 50
Sage 50 cannot update an internal setting in your company file, usually because the file is damaged or locked.
You are seeing the message “Unable to set the file includes headers flag.” In plain terms, Sage 50 tried to change an internal setting stored inside your company file, and the program refused or failed. This is not about page headers on printed invoices, despite how it reads. It is a low-level file operation that went wrong, and it usually points to a damaged or inaccessible company data file.
What the message actually means
The “headers flag” is an internal marker Sage 50 keeps inside the company file. The program sets it when it opens or upgrades data. If the file is damaged, read-only, locked by another process, or held open on a network share, the write fails and this message appears. Sage 50 is telling you it could not update its own bookkeeping inside the file.
Close everything and try again
The safest first step costs nothing. Close Sage 50 completely on every workstation, and make sure no backup job, sync tool, or antivirus scan is touching the company file. Then reopen the company and see if the message returns. On a network setup, check that the machine hosting the data was restarted, since a stale lock on the host can produce exactly this failure.
Check permissions and the read-only state
If the file or its folder is marked read-only, or your Windows account lacks write permission on the data folder, Sage 50 cannot set any internal flag. Right-click the company data folder and confirm it is not read-only, and that your user account can modify files in it. This applies especially after copying a company file from a CD, a USB stick, or an email attachment, all of which commonly arrive read-only.
Restore from a recent backup
If the message repeats, the file itself is likely damaged at the point where this flag lives. Restore your most recent backup to a new location and open that copy. If the restored backup works, the damage is confirmed and you should work from the backup going forward. Do not keep retrying operations on the damaged original; every open attempt adds risk.
When the file needs professional attention
If no backup behaves and the message persists, the data file needs repair rather than more troubleshooting. Our engineers see this pattern in Sage 50 (Peachtree and Simply Accounting) files where internal structures have been corrupted, often after a crash, a power loss mid-write, or an interrupted update. That kind of damage is not fixable from inside the program. We offer a Sage 50 database repair service that works directly on the damaged file, and a free evaluation up front so you know what is recoverable before committing to anything. Cost and turnaround depend entirely on the file, so we quote per case rather than publishing fixed figures.
A useful next step
Make a safe copy of the damaged file now, before trying anything else, and keep it somewhere nothing can overwrite it. Then send us that copy for a free evaluation. Knowing exactly what is wrong costs you nothing, and it prevents well-meaning fixes from making the file harder to recover.