Sage 50 message: "One or more of these files might have been set to 'read-only
Sage 50 is telling you it cannot save changes because the company files are flagged read-only, usually a permissions or lock issue.
You are seeing this message:
One or more of these files might have been set to ‘read-only’.
In plain terms, Sage 50 is telling you it tried to write to your company data and the operating system refused. The files that hold your books are marked read-only at the Windows level, so Sage can open them but cannot save anything. It is a file-permissions problem, not (usually) data corruption, and in most cases it is fixable without touching your accounting data at all.
Why it happens
The read-only flag gets set on Sage 50 data files for a handful of common reasons:
- The files were copied from a CD, DVD, or older backup medium that marks everything read-only by default, and the flag was never cleared after copying.
- Someone copied the company folder from another computer or user account, and Windows applied restrictive permissions to the new copy.
- A backup or sync tool (cloud sync, external drive software) locked the files while it was running.
- A previous crash or improper shutdown left the files in a protected state.
- On a network setup, the Windows user opening the company does not have full read/write permission on the shared folder where the data lives.
Check and clear the read-only flag
Find the folder that holds your Sage 50 company data, right-click it, choose Properties, and look at the Attributes section on the General tab. If the Read-only box is filled in, clear it and apply the change to the folder and everything inside it. Then reopen the company in Sage 50 and try saving something small.
If the box keeps coming back checked after you clear it, something is actively re-locking the files. Pause any backup, sync, or antivirus tool that touches that folder and try again.
Check folder permissions, not just the flag
The read-only attribute and NTFS permissions are two different things. Even with the attribute cleared, the Windows account you are using must have full control over the data folder. This matters most on network installations: the person at the workstation needs write access to the shared folder on the machine hosting the data. If you are unsure where your data folder is, its location depends on how Sage 50 was installed and configured, so check your company setup rather than guessing.
Rule out a leftover lock
If Sage closed unexpectedly, a stale lock file can make the data behave as if it is read-only. Restart the workstation (and the host machine, if networked), then try opening the company again before anything else runs.
When the file itself is the problem
If the flag is cleared, permissions are correct, and Sage 50 still refuses to save or now reports the file as damaged, the data itself may be hurt, often from the same crash or bad copy that set the flag in the first place. Repeated messages, failures to open, or errors after a Verify point to real damage rather than a permissions quirk. In that situation, stop making changes and work from your most recent backup, because every attempted save can make recovery harder.
Damaged Sage 50 (and Simply Accounting or Peachtree) databases are something we repair regularly, and if the worst has happened we can usually recover the data; see our Sage 50 database repair service. If instead you were mid-move to QuickBooks when this appeared, our Sage 50 to QuickBooks conversion handles the data either way.
Next step
Before anything else, make a copy of the entire company data folder while it is in its current state, and keep that copy somewhere safe. That gives you a fixed point to return to no matter which fix you try next. If clearing the flag and permissions does not resolve it, send us the file for a free evaluation and we will tell you what is wrong and what recovery would involve.