Company too big? Purge stops in Payables, lots old data

[cowvets]

I have just 2005 open in PT Premium 2005. My file size in the help, file stats is 203MB after purging what I can. I can purge payables until June of 2004, then it stops at 4% when I try to purge July payables. All other sections purged without problem. Peachtree data verification says no problems. I could not believe that the company file was so big, so did a little digging with Crystal Reports. my largest file is JrnRow at about 132MB. I made a report of all lines in this file by rowdate. I sorted them into month and year. I have 704 rows from 1998 in jrnl 2, 17245 rows from 1999 in jrnls 1,2,3,4,7,9,10. I have 37306 rows in 2000, 44653 rows in 2001, 47942 rows in 2002, 46827 rows in 2003, 87927 rows in 2004, and 69,284 rows in 2005 so far. Seems to me if the purge was going right, I would have 70 less mb in this file (everything prior to 2004 cleaned out).

Does anyone have any suggestions on this?
1. Is the company too big for comfort? Limits I see say 100MB. performance is fine at this point. Our business is fairly stable, so seems we should be fine in keeping to 100MB if the old stuff in here was gone.
2. If the purge does not clean up the company, should I look for data repair?
3. If the purge does not clean up the company, should I rebuild?
4. Is there something I am missing?
Thanks for any help,
Chris

 

[mattjurado]

I'm not a Peachtree expert, but I do work with it from time to time.

Peachtree keeps open a max of 2 accounting years at a time (at least, I'm pretty sure that's it). Have you ever run the end of year process? I don't know if this cleans up the journal files or not, just curious.

Make a copy of the peachw folder (or whereever the data is), before you do anything. I hope you have nightly backups, but if not, do this first.

There is a rebuild option, but I believe you have to start the program with a -i switch (at least I think its -i), so add the switch to your shortcut, you should get the option under your file menu I believe.

Sorry its been awhile, trying to do this from memory. But yes, your data is too big. Another test you might try, copy the directory to your hard drive if its on the network, and see if you can do what you need to do locally, then copy it back up to the network.


Matt J.

Please always take the time to backup any and all data before performing any actions suggested for ANY problem, regardless of how minor a change it might seem. Also test the backup to make sure it is intact.

 

[cowvets]

Thanks for the help. First, I helped another company through many catastrophic data losses, and since I started with PT in 1998, have at least one backup per day. As Kim Komando says, I got the backup religion.

The end of year wizard is not taking out the data from 1998 to 2004 as it should. That is the basis of my question. I have tried to run it locally as well as on the network. I have done the integrity checks (starting with the -i switch enables these options). Nothing out of whack noted. I am about to rebuild (exporting and importing lists of customers, COA, and vendors, etc). I was hoping someone might have advise that would prevent this.
Thanks,
Chris

 

[mattjurado]

So the end of year wizard should have removed that stuff out of your journals, correct?

If so, then I think you are on the right track, that database is too big and you need to manually export stuff out.

Good luck.

Matt J.

Please always take the time to backup any and all data before performing any actions suggested for ANY problem, regardless of how minor a change it might seem. Also test the backup to make sure it is intact.