What are these two files?  Oltrans.dat and Olacct.dat are files for on-line transactions.  Even if you are not using any type of on-line processing for your company, these two files still exist within your Companies dataset.

If they become damaged it may effect some operations within Peachtree.  Most noticeable is a problem with running Data Verification. 

Because of the security system built into Peachtree Accounting you cannot not just copy a file from one company to another.  There is special security built into the system to protect your data.  If the file becomes damaged and you try to copy a file from a different company you will still have problem.

At the time of writing this, there is no way to repair these two files within the Peachtree Software.  DataSoft has developed a special tool to repair them, so you may continue business as usual.

If you receive any messages about oltrans or olacct you either need to restore a backup or have your files professionally repaired by us.

*** NOTE ***  Prior to ever restoring any backup for any software product, ALWAYS make a copy of the current data.   Do this by using the backup feature within the software or copy the data to a new location.  Make sure you name the folders and files to something that will describe to you why it is there.  In the event (and it happens often) that the backup also contains the bad files, you can get back to where you left off.  This allows you to get the damaged repaired without reenter information missing from your old backup.

If you are unsure what you are doing, STOP and find someone that does.   You will save yourself days of work and frustration.

We are receiving more reports from our clients that their Peachtree Accounting General Ledger does not foot after closing the Fiscal Period using the Year-End Wizard.

You may not be aware of this problem until you attempt to run a General Ledger Report or run Data Verification. 

If you run Data Verification review your Datalog.txt file.  If you see errors like:

A ??? transaction dated ##/##/## with reference ### for #.## contains an invalid or illegal accounting period and has been corrected.
( # would be replaced with actual dates, references and dollar amounts. ??? would be replaced with General Journal, Cash Receipts Journal, Sales Journal, etc..)

Also you may see items like: No safe correction is possible.  The transaction has been deleted.

If you are receiving these errors it is because when you closed the fiscal year Peachtree had problems and did not notify you of such.  The screens continue as normal but your files are no updated correctly.  To correct the problem you need to submit your Companies data file to us for repair.  There are no utilities within Peachtree that will resolve this problem.

If you are receiving the error message while viewing a G/L Trail Balance or General Ledger Report in Peachtree Accounting.

At least one damaged transaction has been found in account [???] in the period beginning [xx/xx/xx].  Please run the data verification test to repair the damaged.

We have found this problem happening in two different situations.

1) A Fiscal Year closed failed.
2) A Peachtree Software upgrade.  You converted your companies data to a newer version of Peachtree Software.

Sadly the Peachtree Data Verification test will not resolve the problem.  You will need to have us repair your files. 

If you continue with working with your data without resolving this error, the problem will get worst.
Visit our Peachtree Data Recovery Area

Have you received the error message:

 The Vendor ID that was automatically created already exists in Peachtree.  Manually enter another Vendor ID

 when trying to save a new vendor or maintenance record.

Your data files are damaged and need to be repaired.  We have found this to happen in Peachtree Accounting Version 2007 and higher.  We would assume it could happen with Customers, Inventory or any type of Maintenance Records.

Visit our Data Recovery Page as http://www.mypeachtreedata.com