<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>PeachFuzz &#187; Tips &amp; Tricks</title>
	<atom:link href="http://tristardatasystems.com/Peachtree/blog/index.php/category/tips-tricks/feed/" rel="self" type="application/rss+xml" />
	<link>http://tristardatasystems.com/Peachtree/blog</link>
	<description>Fruitful commentary on Peachtree Accounting from TriStar Data Systems</description>
	<lastBuildDate>Wed, 19 May 2010 17:09:57 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Peachtree Notes and Attachments</title>
		<link>http://tristardatasystems.com/Peachtree/blog/index.php/2009/06/peachtree-notes-and-attachments/</link>
		<comments>http://tristardatasystems.com/Peachtree/blog/index.php/2009/06/peachtree-notes-and-attachments/#comments</comments>
		<pubDate>Thu, 25 Jun 2009 19:38:03 +0000</pubDate>
		<dc:creator>tristar</dc:creator>
				<category><![CDATA[Tips & Tricks]]></category>

		<guid isPermaLink="false">http://tristardatasystems.com/Peachtree/blog/?p=57</guid>
		<description><![CDATA[Here are a couple of tips on Peachtree capabilities that have been present for the last couple of versions, but we find few clients either use or know much about. Notes Sometimes a line item on a customer invoice or a vendor’s purchase order needs explanation, or some additional detail to clarify some part of [...]]]></description>
			<content:encoded><![CDATA[<p>Here are a couple of tips on Peachtree capabilities that have been present for the last couple of versions, but we find few clients either use or know much about.<br />
<strong><span style="text-decoration: underline;">Notes</span></strong><br />
Sometimes a line item on a customer invoice or a vendor’s purchase order needs explanation, or some additional detail to clarify some part of the order. Peachtree gives you an easy way to do this by using the “Notes” button, found on the toolbar for the transaction you are entering.</p>
<p> Clicking the “Notes” button on a sales order, invoice, purchase order, or vendor invoice will open a multi-tabbed window. Typing into the “Customer or Vendor Note” tab will allow you to enter a message up to 2,000 characters in length, and will allow you to print the note on the form, either prior to or following the line items on the form. You can provide a lot more detail on your invoices by putting it into the notes field, rather than trying to add a series of “comment” lines as individual items.</p>
<p> If the note is for “internal consumption only” (perhaps alerting your A/R or A/P clerk to monitor this invoice closely), type the note on the “Internal Note” tab, instead. It will stay with the transaction, but will not print on the form.</p>
<p> <strong>BE CAREFUL WHEN PRESSING THE ENTER KEY</strong>. Pressing “Enter” saves the entry and closes the window. Text entered in the Notes window will wrap automatically. If you need to create a new paragraph but stay on the same note, press CTRL and ENTER at the same time to move to a new blank line but keep the window open.</p>
<p> Unfortunately, Notes are “transaction-related” (i.e., attached to the record) and not “line item” related I.e., attached to a specific item), so if you need to enter a note for a specific line item and not for the record in general, you still need to use the “Comment” approach to place the message in the proper spot on the form.</p>
<p> <strong><span style="text-decoration: underline;">Attachments</span></strong><br />
Attachments in Peachtree work just as the name suggests: you can “attach” any electronic file (spreadsheet, photo, PDF file, Word document, etc.) to either a Peachtree transaction (e.g., an invoice, a journal entry, etc.) or to a “master record” (customer, vendor, job, etc.). Have a photo or a graphic of a particular item you are ordering? Attach the photo to the order. Need to justify a general journal adjusting entry? Attach the letter from your accountant to the entry. Want to show support for your Peachtree budget? Attach the Excel worksheet to the budget.</p>
<p> A couple of “tips and bewares” when working with attachments:</p>
<ol>
<li>You have to first <strong>save the record</strong> before you can <strong>add</strong> an attachment; Peachtree doesn’t know the record is there, and therefore can’t add the attachment, until you first hit the “Save” button. <strong>Then</strong> you can add the attachment to the saved record.</li>
<li>Once a file is “attached” to a Peachtree record, it exists <strong>independent</strong> of the “original” file (Peachtree makes a copy). This means that you can give the attachment a different name than the original, or can even delete the attachment, without effecting the <strong>original</strong> file. It also means, however, that any changes made to the “original” file after attaching it <strong>will not be reflected</strong> in the attachment; once attached there are <strong>two separate files</strong>, each with its own independent existence. If you need to change the original and reflect the change on the attachment, make the change, save the original, delete the attachment, and re-attach to the Peachtree record.</li>
</ol>
]]></content:encoded>
			<wfw:commentRss>http://tristardatasystems.com/Peachtree/blog/index.php/2009/06/peachtree-notes-and-attachments/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Peachtree Budgeting</title>
		<link>http://tristardatasystems.com/Peachtree/blog/index.php/2009/05/peachtree-budgeting/</link>
		<comments>http://tristardatasystems.com/Peachtree/blog/index.php/2009/05/peachtree-budgeting/#comments</comments>
		<pubDate>Fri, 29 May 2009 19:47:55 +0000</pubDate>
		<dc:creator>tristar</dc:creator>
				<category><![CDATA[Tips & Tricks]]></category>

		<guid isPermaLink="false">http://tristardatasystems.com/Peachtree/blog/?p=47</guid>
		<description><![CDATA[In tough economic times (like today) establishing a reasonable budget, and sticking to it through these choppy waters, can mean the difference between navigating successfully to better economic times ahead and crashing on the dangerous financial obstacles all around us. Over the past couple of versions Sage Software has seriously beefed up Peachtree&#8217;s budgeting capabilities, [...]]]></description>
			<content:encoded><![CDATA[<p>In tough economic times (like today) establishing a reasonable budget, and sticking to it through these choppy waters, can mean the difference between navigating successfully to better economic times ahead and crashing on the dangerous financial obstacles all around us. Over the past couple of versions Sage Software has seriously beefed up Peachtree&#8217;s budgeting capabilities, especially in the Peachtree Premium and Peachtree Quantum editions. Just in the nick of time&#8230;.</p>
<p> For virtually everyone, Microsoft Excel is the &#8220;tool of choice&#8221; for designing and calculating budgets. Its &#8220;columns and rows&#8221; orientation make it the ideal tool for interactive, &#8220;what if&#8221; calculations. Excel, however, is not the best tool for maintaining a budget and tracking performance against &#8220;actuals&#8221;. Doing this essential step in Excel requires a lot of extra re-keying, or some complicated exports and imports. Fortunately, Peachtree plays quite nicely with Excel-based budgets these days.</p>
<p> In Peachtree Premium and Quantum, you can establish as many different budgets as you need, and can select any budget to print on your financial statements to facilitate comparisons (Peachtree Complete allows only one budget). Any single budget can reflect up to four years of data: the two currently open fiscal years, plus one year prior to the earliest open year and one year following the latest open year.</p>
<p> Budgeting can be performed for all of your accounts or for any range of accounts, using filters. Especially handy is the filtering available by account &#8220;type&#8221; (income statement accounts, expenses, etc.), or by account &#8220;segment&#8221; (Premium and higher only) to create department-level budgets. An existing Peachtree budget can be easily copied to a new budget, and recalculated using various formulas to test the new assumptions.</p>
<p> The best thing about Peachtree&#8217;s budgeting capabilities, however, is how easily it interfaces with Excel. Import and export buttons are conveniently situated on the budgeting screen toolbar, making it a snap to get your budget data into Peachtree, and equally easy to get it out again for further work in Excel. <strong>TIP</strong>: <em>When building your budget, first set your filters in Peachtree, then export a &#8220;blank&#8221; budget to get all of the relevant accounts quickly and easily into Excel, along with all the appropriate period column headers</em>.</p>
<p> Once you have your &#8220;baseline&#8221; data (accounts and periods) populated in Excel, do all of the normal budget construction directly in Excel, then when the budget is completed send the data back to Peachtree via a CSV file, which is simple to create in Excel (Save As&#8230;).</p>
<p> It is also pretty easy to manipulate some of the budget data directly in the Peachtree budgeting screen, by using the &#8220;Autofill&#8221; button on the toolbar to complete a row, or by using the &#8220;Quick Action&#8221; buttons (Copy and Adjust) accessed via a right click of the mouse anywhere on the cell grid, to modify amounts by a fixed dollar amount, a percentage, or to round to the nearest dollar, hundreds, or thousands.</p>
<p> Peachtree budgeting also works nicely with Peachtree Alerts, to automatically send a message to a selected user when any account is over budget for either a specified period or for the year-to-date budget.  With the Peachtree&#8217;s capabilities to handle attachments to records, you can even &#8220;attach&#8221; the original Excel budget to the Peachtree budget as a fool-proof &#8220;source document&#8221; audit trail.</p>
<p> Peachtree won&#8217;t necessarily help you generate more income, but it can provide the tools you need for creating a good roadmap to follow &#8211; and monitor &#8211; through the twists and turns of a troubled economy.</p>
]]></content:encoded>
			<wfw:commentRss>http://tristardatasystems.com/Peachtree/blog/index.php/2009/05/peachtree-budgeting/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Peachtree Performance Tuning</title>
		<link>http://tristardatasystems.com/Peachtree/blog/index.php/2009/05/peachtree-performance-tuning/</link>
		<comments>http://tristardatasystems.com/Peachtree/blog/index.php/2009/05/peachtree-performance-tuning/#comments</comments>
		<pubDate>Thu, 07 May 2009 20:13:20 +0000</pubDate>
		<dc:creator>tristar</dc:creator>
				<category><![CDATA[Technical]]></category>
		<category><![CDATA[Tips & Tricks]]></category>

		<guid isPermaLink="false">http://tristardatasystems.com/Peachtree/blog/?p=41</guid>
		<description><![CDATA[Everyone wants their software to perform faster, right? Working with a specific application, however, and getting it to run faster on a network can be as much art as science. Here are five general tips for what you can do to improve the performance of Peachtree on your system if you are encountering poor performance. [...]]]></description>
			<content:encoded><![CDATA[<p>Everyone wants their software to perform faster, right? Working with a specific application, however, and getting it to run faster on a network can be as much art as science. Here are five general tips for what you can do to improve the performance of Peachtree on your system if you are encountering poor performance. Some of these things are easy to do and can be handled by users, and some should be &#8220;tweaked&#8221; carefully and left for your &#8220;IT Specialist&#8221; to diddle with.</p>
<ol>
<li> Tweak your anti-virus settings &#8211; Most anti-virus software allows you to define &#8220;exclusions&#8221; to virus checking. You should &#8220;exclude&#8221; the folder where you installed Peachtree on your local drive, as well as the folder and all subfolders on the server where your Peachtree data is stored. This will not likely put your computer in harm&#8217;s way; we have not heard of any malicious software ever infecting a Peachtree .DAT file.</li>
<li>Free up local hard drive space &#8211; You should try to make sure that you have three times the size of your largest company database or 1 Gb, whichever is greater, available as free space on your local hard drive. If Peachtree needs to create a Windows &#8220;swap&#8221; file, this is where it will be parked. Running a &#8220;disk defrag&#8221; on the local drive to optimize the available storage space can also help in some situations.</li>
<li>Edit your Peachtree global settings &#8211; There is a section on the &#8220;General&#8221; tab under the Global Settings menu that allows you to set up &#8220;smart data entry&#8221; rules. While enabling these settings can be handy and make the system more convenient to use, they can also contribute negatively to performance. Unchecking all of the checkboxes in this area may improve speed.</li>
<li>Disable Events- This is an area of Peachtree that we find hardly anyone uses, but it may still be &#8220;activated&#8221; on your system. To turn this off (which can improve performance) click on Tasks, then Action Items, then click on the &#8220;Options&#8221; button on the Action Items menu bar. From the Options menu select the Transactions tab, and uncheck any of the boxes that are checked off in the &#8220;Create Event&#8221; column.</li>
<li>Avoid duplicate transaction reference numbers &#8211; Peachtree allows you to use the same &#8220;reference number&#8221; (e.g., vendor invoice #, cash receipt ID, etc.) as long as you do not use it for the same &#8220;master record&#8221; (vendor, customer, etc.). However, using the same number over and over (e.g., &#8220;cash&#8221; for all deposits) causes the application to work harder when searching and storing information. Keeping all of your &#8220;reference numbers&#8221; unique to the greatest extent possible can improve performance. It can also make life much more pleasant in the unhappy event that you ever need to export and re-import your data; the import will sometimes reject duplicate reference numbers.</li>
</ol>
<p> Of course the most significant contributor to system performance is the size of your Peachtree database, and within that database the single biggest contributor is the Journal Row (JRNLROW.DAT) table within the database. This table holds ALL of your Peachtree transactions, and each time you search for a transaction record the system needs to read through that entire table to find the requested record.</p>
<p> So, how big can this file safely grow to before performance becomes an issue? There is no hard and fast rule for this (still more art than science), but our general &#8220;rule of thumb&#8221; is to begin thinking about maintenance to your database when the journal row table approaches 150,000 total records, <strong>if you are using any version of Peachtree</strong> <strong>except Quantum</strong>. The more powerful <strong>Quantum</strong> product can gracefully accommodate three to four times that number of records without causing significant performance &#8220;degradation&#8221;.</p>
<p> You can review the record count for all of your Peachtree tables by selecting Help | Customer Support and Service | File Statistics from the top menu bar within Peachtree.</p>
<p> Once you have determined the overall size of your Peachtree database and viewed the record counts for the individual tables, you can make a judgment about purging some data. Purging is the process of physically removing selected records from the system, to shrink the overall size of the database. It can, however,  be a time consuming and technically daunting task, since there are any number of &#8220;gotchas&#8221; that can impede or abort the purge process.</p>
<p>We have assembled a set of instructions for performing Peachtree database purges on our website, which you can review by <a title="Purging Peachtree data" href="http://www.tristardatasystems.com/clientcontent/PTcontent/PTpurging.html" target="_blank">clicking here</a>. In some circumstances it is more cost-effective to use an outside data repair service to fully purge records that are no longer needed in the system. And in all cases, it is good practice to make an &#8220;archive&#8221; copy of the database before starting a purge. Peachtree Premium makes the archiving process easy, but Peachtree Complete users can create &#8220;manual&#8221; database archives.</p>
<p> Carefully following these &#8220;best practices&#8221; for Peachtree data storage will help you to get maximum performance from your Peachtree software.</p>
]]></content:encoded>
			<wfw:commentRss>http://tristardatasystems.com/Peachtree/blog/index.php/2009/05/peachtree-performance-tuning/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Managing Reports and Forms</title>
		<link>http://tristardatasystems.com/Peachtree/blog/index.php/2009/04/managing-reports-and-forms/</link>
		<comments>http://tristardatasystems.com/Peachtree/blog/index.php/2009/04/managing-reports-and-forms/#comments</comments>
		<pubDate>Thu, 02 Apr 2009 14:19:34 +0000</pubDate>
		<dc:creator>aphillips</dc:creator>
				<category><![CDATA[Tips & Tricks]]></category>

		<guid isPermaLink="false">http://tristardatasystems.com/Peachtree/wordpress/?p=12</guid>
		<description><![CDATA[Peachtree offers a significant amount of customization capability for the reports and forms generated by the product.  Sometimes in our rush to make  modifications to existing reports, to suit our specific needs, we neglect to think through an organizational structure for managing these changes, resulting in what we term &#8220;Turbo Chaos&#8221;. Here are a few [...]]]></description>
			<content:encoded><![CDATA[<p>Peachtree offers a significant amount of customization capability for the reports and forms generated by the product.  Sometimes in our rush to make  modifications to existing reports, to suit our specific needs, we neglect to think through an organizational structure for managing these changes, resulting in what we term &#8220;Turbo Chaos&#8221;.</p>
<p>Here are a few tips for managing your modifications to Peachtree reports and forms:</p>
<ol>
<li>As soon as you begin to make changes to a standard report, change the report title from the &#8220;standard&#8221; title to something more descriptive of the specific objective you are trying to achieve (e.g., Bookkeeper&#8217;s A/R Reconciliation&#8221;). With each revision to the report, save it as a &#8220;new&#8221; version, with the version number in the title, until you have it <strong>exactly</strong> as you originally envisioned the report. Then &#8211; <strong>and only then</strong> &#8211; delete all the &#8220;earlier&#8221; versions, and change the report title to reflect what you want to appear each time you run it.</li>
<p><span style="color: #ffffff;">&lt; /br&gt;</span></p>
<li>When modifying Peachtree forms, include the date of the revision in the name of the form (e.g., TriStar AP Check 021508). Again, track versions with each &#8220;save&#8221; until you get the form the way you want it, then delete all the versions except the one you want to use. Retain the date in the form name so that you will be able to easily track when it was originally designed.</li>
<p><span style="color: #ffffff;">&lt; /br&gt;</span></p>
<li>Peachtree organizes the Reports Menu, by default, with all &#8220;custom&#8221; reports listed first within a report group, followed by all &#8220;standard&#8221; reports. Within these two groups individual reports are sorted in standard &#8220;computer sort&#8221; order, which is to say numbers (treated as text) first, followed by letters. Thus 1 and 10 come before 2, and all three come before &#8220;a&#8221;. So, if you have a desired order for your custom reports on the menu, apply a little creativity to the naming convention, using a combination of numbers and letters to achieve the desired result.</li>
</ol>
]]></content:encoded>
			<wfw:commentRss>http://tristardatasystems.com/Peachtree/blog/index.php/2009/04/managing-reports-and-forms/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
