Peachtree Limitations

[wen_dell8]

is there anybody knows all the limitations of Peachtree Premium Accounting for Distribution 2004. my main concerns is the storage capacity and the number of users it can handle in the network. :eek:

[rick Prindivill]

Peachtree's EULA states a maximum of 5 concurrent users.

Peachtree does not define any theoretical limits for the number of Comapanies, GL COA's, Customers, Vendors etc.

You may want to propose what you think your practical needs might be and other can then comment based on their experience

Please note that your version of Peachtree 2004 uses Btreive 6.15 DB Engine, while the current Peachtree 2007 uses Pervasive SQL 9.0 DB Engine. Peachtree 2007 is using essentially the same database but with a more powerful database engine. Results, is larger databases and more records. The EULA is limited to 5 named users, while its big brother Quantum is limited to 10 users, again the same database and the same database engine.

[wen_dell8]

thank you very much sir for your information.

[wen_dell8]

sir our superior wanted to know is there any maximum limit of file size for Peachtree Premium Accounting for Distribution 2004.

[TheWolf]

There is not a maximum limit where it will just stop, accept for the number of transactions tied to a specific customer or vendor ID, which is about 16000. Once the database gets between 150 to 200 mb in a multi user system it becomes less effective and may become more prone to corruption. 1500 transactions a month is an approximation.

Make sure to do a purge after every year end close and this will help reduce database size by removing transactions.

[Robert Walraven]

2004 has a maximum file size limitation of 2 GB, which is a limitation both of Btrieve 6.15 and of the zip utility that Peachtree uses. But I have never seen a 2004 database that comes even close to this.

Since 2007 flavors upgraded to a newer version of Pervasive software, Btrieve now can allow recordsets up to (I think) 64 GB by breaking the recordset into 2 GB files. For example, if you see JrnlHdr.dat and JrnlHdr.^01
in your database, the first file will be 2 GB and the second one will contain the remainder of the records.

The 2 GB limitation on file size means that the ZIP utilty that Peachtree uses will continue to work as long as the size of the compressed file does not exceed 2 GB.

This became an issue with Quantum because it turns record compression off, which makes the files enormously bigger, so it is a lot easier to exceed a 2 GB backup. And if you can't back up then you also can't close the year, run Data Verification, etc. However, I believe that Peachtree has corrected this problem with a recent service release. Can anyone confirm that?

[pmccomack]

You can get around the 2 GB ZIP limit temporarily by moving the offending files (probably jrnlrow.dat) before the backup and moving them back afterward. This creates an incomplete backup of course so make sure to create a true backup with WinZip/WinRAR which do not have a 2 GB file size limit.

I've found that the true limit for 2004 is just short of 4 GB, at least for jrnlrow.dat. You'll definately want to make plans before it gets close to the 4 GB mark though. Once you pass 3.98ish GB Peachtree will start throwing file system errors and you will be in for a difficult rebuild.