Comments for PeachFuzz http://tristardatasystems.com/Peachtree/blog Fruitful commentary on Peachtree Accounting from TriStar Data Systems Thu, 08 Dec 2011 17:16:47 +0000 hourly 1 http://wordpress.org/?v=3.3.1 Comment on Paying Vendor Invoices via Credit Card by Khurram http://tristardatasystems.com/Peachtree/blog/index.php/2011/02/paying-vendor-invoices-via-credit-card/comment-page-1/#comment-177 Khurram Thu, 08 Dec 2011 17:16:47 +0000 http://tristardatasystems.com/Peachtree/blog/?p=109#comment-177 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 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 http://tristardatasystems.com/Peachtree/blog/index.php/2009/06/peachtree-notes-and-attachments/comment-page-1/#comment-128 Philip Fri, 10 Jun 2011 19:49:17 +0000 http://tristardatasystems.com/Peachtree/blog/?p=57#comment-128 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. 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 http://tristardatasystems.com/Peachtree/blog/index.php/2009/08/optimizing-peachtree-performance/comment-page-1/#comment-62 Timothy Seibert Fri, 29 Oct 2010 15:20:31 +0000 http://tristardatasystems.com/Peachtree/blog/?p=83#comment-62 Thank you for the quick Reply I will get right on that. Thank you for the quick Reply I will get right on that.

]]> Comment on Optimizing Peachtree Performance, Part 1 by tristar http://tristardatasystems.com/Peachtree/blog/index.php/2009/08/optimizing-peachtree-performance/comment-page-1/#comment-61 tristar Fri, 29 Oct 2010 15:02:52 +0000 http://tristardatasystems.com/Peachtree/blog/?p=83#comment-61 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. 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 http://tristardatasystems.com/Peachtree/blog/index.php/2009/08/optimizing-peachtree-performance/comment-page-1/#comment-60 tristar Fri, 29 Oct 2010 14:52:08 +0000 http://tristardatasystems.com/Peachtree/blog/?p=83#comment-60 Not if the new computer is running Vista or Windows 7. Time to upgrade that ancient Peachtree license! 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 http://tristardatasystems.com/Peachtree/blog/index.php/2009/08/optimizing-peachtree-performance/comment-page-1/#comment-59 Timothy Seibert Fri, 29 Oct 2010 14:43:49 +0000 http://tristardatasystems.com/Peachtree/blog/?p=83#comment-59 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. 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 http://tristardatasystems.com/Peachtree/blog/index.php/2009/05/peachtree-performance-tuning/comment-page-1/#comment-58 tristar Thu, 12 Aug 2010 14:05:19 +0000 http://tristardatasystems.com/Peachtree/blog/?p=41#comment-58 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. 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 http://tristardatasystems.com/Peachtree/blog/index.php/2009/05/peachtree-performance-tuning/comment-page-1/#comment-57 Les Mcglinchey Thu, 12 Aug 2010 13:50:18 +0000 http://tristardatasystems.com/Peachtree/blog/?p=41#comment-57 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! 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!

]]> Comment on Optimizing Peachtree Performance, Part 1 by Joan http://tristardatasystems.com/Peachtree/blog/index.php/2009/08/optimizing-peachtree-performance/comment-page-1/#comment-56 Joan Mon, 26 Jul 2010 23:08:56 +0000 http://tristardatasystems.com/Peachtree/blog/?p=83#comment-56 I have Peachtree complete accounting 2005. Will my program work on a new computer with dual processor? I have Peachtree complete accounting 2005. Will my program work on a new computer with dual processor?

]]> Comment on Sage Peachtree 2011 – First Look by Andrea Moe http://tristardatasystems.com/Peachtree/blog/index.php/2010/05/105/comment-page-1/#comment-53 Andrea Moe Wed, 19 May 2010 20:01:42 +0000 http://tristardatasystems.com/Peachtree/blog/?p=105#comment-53 Thanks for this review, Jack! Tweeting this now :) Andrea Thanks for this review, Jack!

Tweeting this now :)

Andrea

]]>