PDA

View Full Version : Corrupted Report.Dat due to incomptatible print driver


Lorin Browning
05-11-2007, 07:07 PM
In a previous message, LauraG's comments gave me great advice on how to deal with a corrupted report.dat file. I regularly access six different companies in Peachtree and only one (company X) still has a problem that will not let me delete several financial statements that I want to modify or, at a minimum, to get rid of.

Since I am getting ready to upgrade from Peachtree Complete Accounting 2005 to a newer version, I have two areas of concern.

(1) If I install a new version of Peachtree and access company X, will I still have the same financial statements that I will not be able to change or to delete?

(2) Even if the answer to the above is "No" but especially if the answer to the above is "yes", is there any way that I can delete all financial statements for company X only in my current version of Peachtree? If I could just simply wipe out all existing financial reports for only that company, I can easily design new financial reports (with a generic print driver) and feel more secure before I upgrade Peachtree.

I guess my questions are:

(1) Does the corrupted report.dat contain the reports for all my Peachtree companies, or is there a report.dat for each company?

(2) Will that corrupted report.dat corrupt its analogue in the newer version of Peachtree?

(3) If there is only one report.dat for all companies, is it feasible to delete that file and then re-install my current version of Peachtree to obtain an uncorrupted report.dat?

Thanks for your help.

LauraG
05-12-2007, 07:47 AM
From what I can see each company has its own Report.dat as well as Rptdata.dat so if one company's file is corrupt then it won't impact your other company's reports.

One of the things discussed over on the Yahoo Peachtree group was the concept of sharing the Report.dat file amongst our various companies and versions. A little bit of experimenting revealed that we could copy the Report.dat file from one company folder to another. We could also copy one from 2004 into 2005 or 2006. I did not test copying into 2007 so I don't know if it would work.

Another idea we explored was the idea of creating a dummy company file and copying the reports into this dummy company file. This allows for sharing standard custom reports bwt versions and companies. You could do this to create a good Report.dat file - just don't pull any reports in from the company file that has the corrupted Report.dat file. Then replace the Report.dat file that is corrupt.

Just be aware that this might happen again in the future. Incompatible printer drivers seems to be common problem with PT. It does not seem that PT keeps up with newer printer models available. They seem to be stuck on the old HP Laser II or Laser III as "safe" printers to use.