Sage 50 you cannot save these changes

Sage 50 you cannot save these changes

Sage 50 Help & Error Resolution

Sage 50

Sage 50 you cannot save these changes

This error may be many different issues. Make sure you are not trying to edit an archived company. You can tell this by looking at the Sage 50 program title bar. Make sure it does not say Archived (company name), you cannot edit an archived company.

If you are not working with an archived company then your company’s DDF (Data Dictionary Files) may be damaged. The DDF files provide the database schema (database layout) to the Sage 50 database.

You can delete these files and Sage 50 will create a new set for you when you open your company again.

Sage 50 / Peachtree
Data Recovery

Always backup your company’s data before deleting any files.  We cannot stress this enough.  If you delete the wrong files by error you can easily get them back by restoring your backup. 

Locate your company data folder. If you are running Sage 50 2021 you may find this on the open company dialog. If you are running an older version. Open the company, from the top menu select Maintenance, and select Maintain Company Info.

Once you have your company’s data location at hand, close the Sage 50 program. Make sure any additional users have the company closed as well. The company cannot be in use when we are going to delete the DDF files.

Open Windows File Explorer and navigate to the data folder above.

Delete all the DDF files.

Restart Sage 50 and open the company.  You should see a flash dialog showing that it is recreating the DDF files.

That’s it.  Now see if the message “You cannot save these changes.” has stopped.

Related Articles

Browse All Categories

No Results Found

The page you requested could not be found. Try refining your search, or use the navigation above to locate the post.

Unable to determine security privileges Sage 50 / Peachtree

Sage 50 Help & Error Resolution

Sage 50

Sage 50 and Peachtree Accounting Software - Unable to determine security privileges. Please retry later. This is probably due to another user temporarily blocking access to critical files.

This error is caused by damaged .dat files.  It has nothing to do with User Security or any other user’s rights issues.  Sage 50 or Peachtree is trying to open a file that has been damaged.

The damage is normally caused by:

  • A workstation losing connection to the Company’s database.
  • Workstation lockup or reboot while Sage 50 was open.
  • Network issues that broke the connection to the open database.
    Power failed while using Sage 50 or Peachtree Accounting.
  • This is not a damaged program problem it is a data file problem.

This causes the files to not be properly updated and left in an invalid state. We have found that most of the time that pieces of transactions will be missing and totals will not be updated correctly. It normally affects multiple files and your main transaction files (jrnlhdr.dat and jrnlrow.dat).

There may also be times when the damage could have happened weeks prior and because you have not hit that damaged area within the file and never received the error message. Once you receive the error message you will be unable to continue until it has been resolved.

There are only two options to resolve the problem:

  1. Either restore a backup prior to the damage
  2. Have your Company files repaired by our Data Recovery Service.

If you decide to restore from a prior backup, make sure you run the Data Verification process from the File Menu once the backup is restored. You will also have to reenter any maintenance records and transactions since the timeframe of your backup.

You will need to research why the Security Privileges Error happened.

  • Ask users if they encountered any problems while working in Sage 50.
  • Other applications that may have caused the workstation to lock or reboot.
  • Check Windows Application and Services Logs in the Control Panel for Events.
  • Check your network wiring and patch cables.
  • If your environment has power surges or drops, install an Uninterruptible Power Supply (UPS) to all workstations including the File Server (if used).

Sage 50 / Peachtree
Data Recovery

Related Articles

Browse All Categories

No Results Found

The page you requested could not be found. Try refining your search, or use the navigation above to locate the post.

At least one damaged transaction has been found in account [Account ID] in the period beginning

Sage 50 Help & Error Resolution

Sage 50

This Sage 50 error message notifies you that there are damaged transactions.

  • If the beginning period is within the current 2 open years, Data Verification should fix it.
  • If the period is outside of your open 2 years your data will have to be repaired using our Sage 50 Data Repair Service. This is because Sages 50 Data Verification option only works the 2 open years of data.

You will receive the error message while running a General Ledger report. The error may not appear until you select a range of periods to report.  If you run your report by Date Range it will not show you any errors.

Running Sage 50 Data Verification

  1. From the top menu select File and then Data Verification.
  2. Select Both Tests, and then click Start.
  3. Enter a New Backup File Name. Never overwrite an existing backup file.  Always name your backup file to something that is useful and unique. If you run Data Verification multiple times always give the backup file name a different name. Data Verification will start automatically after the backup has completed.
  4. After the process has finished run a General Ledger report (with a large period range) to see if you still receive the error.

If you still receive the error you will need to submit your data for our Data Recovery Service.

Sage 50 / Peachtree
Data Recovery

Related Articles

Browse All Categories

No Results Found

The page you requested could not be found. Try refining your search, or use the navigation above to locate the post.

Fixing Repaired Maintenance Records – Sage 50

Fixing Repaired Maintenance Records – Sage 50

Sage 50 Technical

Sage 50

Restoring Missing Maintenance Data in Sage 50

If any of your Sage 50 maintenance records—such as Customers, Vendors, or Inventory Items—have been damaged, some information may be missing and require manual updates.

Why Does Data Loss Occur?

When Sage 50 files become damaged, they often lose essential data stored in their respective fields. As part of DataSoft's repair process, we create new records and attempt to populate them using information from related transactions. However, much of the field-specific data may not be recoverable and will need to be manually re-entered.

What Data Needs to Be Restored?

Most missing data pertains to cosmetic fields, including:

  • Maintenance Record ID (Customer ID, Vendor ID, etc.)
  • Mailing addresses
  • Default G/L Account IDs
  • Phone numbers

While these details require manual updates, rest assured that balances and transactions within damaged maintenance records will be fully corrected, ensuring the accuracy of the accounting portion of your dataset.

Important Note on IDs

Original Customer, Vendor, and Inventory IDs cannot be retrieved, as they are stored exclusively within the maintenance record fields.

How to Fix Missing Maintenance Data

  • Identify Temporary Records: DataSoft assigns temporary IDs (e.g., XXX- or ZZZ-) to newly created maintenance records. Locate these records.
  • Update the ID: Use the Change ID button at the top of the maintenance screen to assign the correct ID.
  • Verify and Edit Field Information: Ensure that all missing details—such as mailing addresses and default G/L accounts—are updated. Be mindful that default G/L accounts may be located under different tabs on the maintenance screen.

By following these steps, you can restore missing data efficiently and ensure your Sage 50 records remain accurate and functional.

Sage 50 / Peachtree
Data Recovery

Related Articles

Browse All Categories

No Results Found

The page you requested could not be found. Try refining your search, or use the navigation above to locate the post.