DDE is implemented similar to the Import/Export function in Peachtree. Thus, if you're having a problem poking information into Peachtree, try exporting some transactions out of Peachtree, then take a look at the resulting .CSV file. For instance, to poke Sales Tax into a Invoice transaction, the sales tax calculation must be the first line of the distribution. If it isn't, you simply won't be able to poke sales tax into Peachtree.

If you're new to using DDE with Peachtree Accounting, it's best to start out by using DDERequest to extract information from Peachtree. It's hugely easier to get information out of the program, but you can, with some perseverence, successfully get data into the program.

When it works, using DDE with Peachtree is fantastic. However, building a successful DDE solution requires a lot of trial and error. Good code samples are few and far between, particularly in the Peachtree documentation. The best advice that we can offer is when you're starting out, keep things simple! If you're trying to poke data into Peachtree, send over only the minimum information required to create a transaction. Only after you can get the basics to work should you then try to add complexities such as multiple distributions and additional fields.

There's even more fun if you're working with inventory items via DDE. You can only extract the quantity on hand from Peachtree via DDE (that field isn't available for text import). Fair enough, but you can't export the current item cost for a stock item via DDE. That gem can only be extracted from Peachtree via text file. So, if you need both the Quantity on Hand AND the Item cost, you get to create a solution that involves both DDE and exporting via text file. It's just a blast!
Update: Version 8.02 and later of Peachtree allow you to export the Quantity on hand to a text file.

If you're extracting inventory items, in the line item file the field REORDERQTY corresponds with the Minimum Stock field, while ORDERQTY corresponds to Reorder Quantity. Yes, this is does appear to be backwards, but much of how DDE is implemented in Peachtree calls for reverse logic.

Want to pull transaction data from other than the current period? Use the following syntax:
"File=journalname,KEY=PER=period#,Field=fieldname"

Also keep in mind that if the Peachtree company that you're accessing is password protected, in Peachtree 6.0 and later you have to send the user id and password together, i.e. JoeUserJoePassword.

As you're probably aware, the password security in Peachtree Complete Accounting 6.0 and later is greatly improved over previous versions. You can now limit access on a screen-by-screen basis. Even better, you can set up a user ID that ONLY allows DDE access. Thus, you can also set the password to DDE. Storing DDEDDE in your app means that if someone happens to trip through your code, they'll only gain access to a password that won't let them do anything at all within Peachtree.

If you're extracting Inventory items, in the line item file the field REORDERQTY corresponds with the Minimum Stock field, while ORDERQTY corresponds to Reorder Quantity. Yes, this is does appear to be backwards, but much of how DDE is implemented in Peachtree calls for reverse logic.

Want to pull transaction data from other than the current period? Use the following syntax:

"File=journalname,KEY=PER=period#,Field=fieldname"