This account is currently in use and cannot be saved" in Sage 50
Sage 50 thinks another user or session still holds the account record open, so it refuses to save your changes until the lock clears.
You see this when you try to save changes to an account in your chart of accounts:
This account is currently in use and cannot be saved.
Despite the wording, the problem is usually not another person typing in the same account. It means Sage 50 believes the account record is locked by an open session, a transaction, or a stale lock left behind after a crash. The software will not overwrite a record it thinks someone else is editing, so it blocks the save rather than risk two conflicting versions of the same account.
Why the lock exists
Sage 50 locks records so two users cannot change the same thing at once. In a multi-user setup, the lock may genuinely belong to a colleague who has the account, a journal entry, or a report using it. More often, the lock is stale: a workstation lost its connection, Sage 50 was closed improperly, or a background process never released the record. The software cannot always tell the difference, so it plays it safe.
Check for other users first
Ask everyone on the network to close Sage 50, then reopen your company and try the save again. If it works, someone really did have the account open. If you are the only user and the message still appears, the lock is leftover debris, not a live person.
Restart Sage 50 cleanly
Close Sage 50 on your machine and wait a moment before reopening. On a network setup, the person hosting the company file should also restart their Sage session. This clears most temporary locks. If the message returns immediately, do not keep retrying; repeated saves against a stuck lock can leave the record in a half-updated state.
Restore from a recent backup
If the lock refuses to clear and the account will not accept changes, restore your most recent backup to a new location and test the account there. This tells you whether the problem lives in your working file or in the session. Never restore over your live file while testing.
When the file itself is damaged
A lock that survives restarts, single-user mode, and a restore test often points to real damage inside the company database. The account record, its transaction links, or the locking tables may be inconsistent. Continuing to work in the file risks spreading the inconsistency, so stop making changes and get the file looked at.
Our engineers repair damaged Sage 50 (Peachtree and Simply Accounting) databases regularly, including records that will not save and locks that will not clear. If you would rather move the data out entirely, we also handle Sage 50 to QuickBooks conversions. Either way, start with a free evaluation: send us the file and we will tell you what is wrong, what it takes to fix, and what it costs, with no obligation.