Speed/size issue & advice

[gmeeks]

We are using Peachtree complete 8.0 with 4 networked users and are trying to decide whether to upgrade or to switch to a higher end product (Mas90, etc.). I like Peachtree (& Pawcom), but I suspect we've just outgrown it. It has become painfully slow, but I would love any advice on how we could stay with Peachtree and avoid retraining, data transfers, $$$, etc.

I think I've followed most of the advice here (turning off virus programs, checked potential network probelms, etc.). I haven't been able to successfully purge - it ran over the holiday weekend trying to purge 6 months data but didn't finish. I'm going to try purging very small pieces and see if I can get those to complete at night.

Our overall file size is 142,000 Kb for 14 months of data (83,318 Kb in JrnlRows).

Are there supposed to be any speed improvements in version 2003? Are these file sizes reaching practical limits of PT or is it possible to make PT operate effectively with this type of volume?

Thanks to anyone for advice!

[dringstrom]

The only info that I have on Peachtree 2003 regarding speed is that the purge function has been rewritten. Perhaps it will actually work now...I've had very mixed results in the past.

You're definitely hitting the upper tier of Peachtree, but one idea if you can't get the purge to work is to rebuild your company. You'd keep the existing company in place for research purposes, but import your lists into a new company. This would definitely knock down the size of your JrnlRows file. Indeed, purging or rebuilding might become an annual event.

Another idea, since you're using PawCOM, is to see if you can store more of your data in Access, then just post summary information into Peachtree.

Hope this helps!

[Rick]

The problem with most purges is that it will NOT get rid af any data in open periods. Even 2003 and its new purge would only get rid of list data that has never been used. Since you said you've only 14 months so far in peachtree and your data is already that large, I would recommend you consider something a little more robust like MAS90. Yeah its expensive as Hell but if you are dealing with that many transactions and considering the efforts it takes to constantly rebuild and purge and rebuild and purge, then in the long run it will probably balance out.

[chuayp]

Our system is also slowing down especially when you want to recall some posted file. It take 1 or 2 minutes to retrieve.

We try to purge data and close year end process. It only help a little bit.

Unless Peachtree change their database to SQL server or else we will facing this long long time in our coming transaction.

Best Regards

Chua