Purchase Order data

I could really use some help finding the tables and fields that contain the items on a purchase order. This would be Item, Quantity. Description, Cost, etc. I have looked at all of the fields in JrnlRow and found nothing usable. The documentation (for Peachtreee) mentions the Project table, but there is none. So any explaination of how all of this goes together would be helpful.

Thanks, Dave

Reply to
Dave Boland
Loading thread data ...

I forgot to mention that the intention is for a Crystal report purchase order form. However, I'm beginning to feel that the data I need may not be readily accessible to Crystal.

Reply to
Dave Boland

If you go to Import/Export on the File menu there may be a choice for importing or exporting purchase order data. Select one of these and bring up the context sensitive Help. You should be able to find table and field descriptions there. I've never done it for a purchase order but I have done it for sales receipts. I know that it's available for most transactional procedures.

Reply to
Wayne Morin

You could contact Bob Walraven at Multiwareinc.com Their Pawcom product will let you query peachtree data. Peachtree was supposed to be exposing their data via XML and exposing all their data via an SDK. Not sure if that is out yet or not.

HS

: > Thanks, : > Dave : >

: : I forgot to mention that the intention is for a Crystal : report purchase order form. However, I'm beginning to feel : that the data I need may not be readily accessible to Crystal. :

Reply to
HSalim

Thank you for the replies. I'll look at the Multiwareinc product to see if it will help. The SDK is available, and it is free -- kind of. You have to register, give a lot of confidential information, and then they will contact you. My take on it is that it is for major players, not a programmer doing some limited work for an accounting firm. Besides, I don't know that the SDK documentation is any better than the product documentation. The reason it has been a pain is the poor documentation supplied by Peachtree. To use a car analogy, they describe all the controls on the car, but not how to drive it. They could do better.

I tried the Import/Export idea, but found that many of the tables used are not exposed to Crystal. I have found most of the data in JrnlRow table, but getting there is not very straight forward (see comments above).

Dave,

Reply to
Dave Boland

I have know Bob Walraven from the time I bought one of the earliest versions of PAWCom (or PAWet as it was called then). Bob has a deep understanding of peachtree's data structures and logic because he had to reverse-engineer his way into the data. In those days we were having some difficulty with the inventory cost data.

Thanks to all that trial and error reverse engineering, Bob is probably the most knowledgeable person outside the company. Even so, I am sure there are a few things that are grey areas to him as well. Inspite of being a recognized PT partner and all, there are still a few things about their data that the PT folks just do not reveal.

HS

: > Thanks, : > Dave : >

: : Thank you for the replies. I'll look at the Multiwareinc : product to see if it will help. The SDK is available, and : it is free -- kind of. You have to register, give a lot of : confidential information, and then they will contact you. : My take on it is that it is for major players, not a : programmer doing some limited work for an accounting firm. : Besides, I don't know that the SDK documentation is any : better than the product documentation. The : reason it has been a pain is the poor documentation supplied : by Peachtree. To use a car analogy, they describe all the : controls on the car, but not how to drive it. They could do : better. : : I tried the Import/Export idea, but found that many of the : tables used are not exposed to Crystal. I have found most : of the data in JrnlRow table, but getting there is not very : straight forward (see comments above). : : Dave, :

Reply to
HSalim

BeanSmart website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.