Comments for PeachFuzz

Comment on Automating Your Peachtree Backups by tristar

tristar — Tue, 06 Mar 2012 14:29:34 +0000

This does not sound correct to me. A Peachtree backup made by the program will always create a file with a .PTB extension. DotNetZip is the name for a “component” of the Peachtree interface (actually it is a Microsoft technology, used by various web-based applications). I would advise you to delete the backup definition file you have created (should have an extension of .PTC), and start fresh by creating a new backup definition file from within Peachtree, stoirng the output in a dedicated folder within the “Company” folder (but not in the folder that actually holds the company data files). Backups are much easier to monitor and manage if you create them in a separate folder. We always recommend creating a folder called “Backups” and placing it within the folder called “Company” whereever your Peachtree data is stored.

Comment on Automating Your Peachtree Backups by James McDonald

James McDonald — Tue, 06 Mar 2012 08:04:08 +0000

Peachtree Large Backup of 3.1GB (Includes Attachments)
When backup to a Flash drive it does not use the
“Kelpro Incorported-030612.ptb” which with Attachments is 3.15GB
It give this name { “DotNetZip-jrmogash.tmp” with File Size1.4gb }
But a do a manual back to flash drive it uses the Correct Name
“Kelpro Incorported-030612.ptb”
Is the DotNetZip used in Peachtree to reduce File Size.?

Manual Backup takes less that 20 minutes.
Automatic Backup takes over 1 Hour.

Any ideas. Is DotNetZip included in Peachtree 2011.?
Has some one installed some rogue software on Server Computer that is causing the problem.?
Thank you.!..

Comment on Paying Vendor Invoices via Credit Card by Khurram

Khurram — Thu, 08 Dec 2011 17:16:47 +0000

i just want to know if we make prepayment to vendors through credit card account type of credit card is cash accout or liablity account

i am realy impress ur images guide line.
Thanks
Khurram

Comment on Peachtree Notes and Attachments by Philip

Philip — Fri, 10 Jun 2011 19:49:17 +0000

The one question I have about this image attachement is where does Peachtree store the copy? We were hoping to add attachements to all items then use these attachement to help redo our website, but we are unable to determine where Peachtree stores the attachments. Any input would be greatly appreciated.

Comment on Optimizing Peachtree Performance, Part 1 by Timothy Seibert

Timothy Seibert — Fri, 29 Oct 2010 15:20:31 +0000

Thank you for the quick Reply I will get right on that.

Comment on Optimizing Peachtree Performance, Part 1 by tristar

tristar — Fri, 29 Oct 2010 15:02:52 +0000

Part 2 never got published because Peachtree went to Pervasive 10 when they rolled out Peachtree 2010 (and now Peachtree 2011), which is a different beast entirely from Pervasive 9.x. The Old Version 9.x tricks don’t seem to work with the 10.x engine, and my tech buddies have not yet figured out an acceptable tuning protocol for this version of Pervasive that adds any significant performance boost to Peachtree.

Having said that, I can tell you that the single biggest performance killer in Peachtree is the size of your JrnlRow.DAT file. If you go to Help | Customer Support and Service | File Statistics, you can check both the number of records and the file size for each Peachtree table. If your Journal Row file exceeds about 200,000 records, you will notice significant performance bottlenecks. The solution to this is to do a purge. Many users think that these old records are automatically purged when year end closing is performed, but they are not. They hang around forever until they are removed via the purge process. There is a whole set of “lore” associated with best practices for performing purges on large databases, which you will want to be aware of before starting this process.

And based on your post, if I am correctly inferring that you may have 7 users hitting your server via terminal services, you are WAY under spec with only 4 Gb of RAM. If you were running Peachtree 2011 on Server 2008 (which works just fine) I would recommend 1 Gb RAM per user, PLUS 4-8 Gb for the server itself. Sounds like that box should have about 16 Gb RAM to run efficiently.

Comment on Optimizing Peachtree Performance, Part 1 by tristar

tristar — Fri, 29 Oct 2010 14:52:08 +0000

Not if the new computer is running Vista or Windows 7. Time to upgrade that ancient Peachtree license!

Comment on Optimizing Peachtree Performance, Part 1 by Timothy Seibert

Timothy Seibert — Fri, 29 Oct 2010 14:43:49 +0000

Where’s Part 2?
I’ve covered everything written here, and I still have some unhappy bookkeepers who want to know why peachtree is so slow.

Comment on Peachtree Performance Tuning by tristar

tristar — Thu, 12 Aug 2010 14:05:19 +0000

Thanks for the kind words. Given that Peachtree is a “moving target” with new releases annually, we will plan to revisit this topic sometime over the fall, to see what is changed with the 2011 Peachtree release.

Comment on Peachtree Performance Tuning by Les Mcglinchey

Les Mcglinchey — Thu, 12 Aug 2010 13:50:18 +0000

I think this article was probably a sweet start to a potential series of write ups about this topic. A lot of writers act like they comprehend what they are preaching about when it comes to this stuff and generally, nearly no one actually get it. You seem to know about it though, so I think you should run with it. Thank you!