payable and receivable


P

pago_boss

Hi Folks,

I am using quickbooks accounts payable and receivable modules and i
wish to know how the various tables in the modules are linked with
each other. Can anyone explain to me how these payable and receivable
tables are actually linked in quickbooks.

Thanking you in advance.


pago
 
Ad

Advertisements

A

Allan Martin

Hi Folks,

I am using quickbooks accounts payable and receivable modules and i
wish to know how the various tables in the modules are linked with
each other. Can anyone explain to me how these payable and receivable
tables are actually linked in quickbooks.
ones and zeros.
 
G

Gary E

Maybe you could tell us how you think it works, and we can assist you from
there

Gary
 
A

Allan Martin

Gary E said:
Maybe you could tell us how you think it works, and we can assist you from
there
Or even better what the hell you are talking about.
 
P

pago_boss

Or even better what the hell you are talking about.







- Show quoted text -
i am talking about the database designs and relationships for the
tables.

thanks,

pago
 
P

pago_boss

Maybe you could tell us how you think it works, and we can assist you from
there

Gary









- Show quoted text -
The accounts payable database, for example, have the following tables:

Purchase order:
Purchase order number
Order nbr
Purchase order type
Payable entity
Customer id
Vendor id
Vendor location
Buyer id
Etcetra....

Payment:
Payment method
Pay_reference number
Pay_date
Vendor Id
Vendor Name
Vendor_Address
Bank Account
Pay amount
Journal Id
Etcetra....

Payment request line:
Vendor ID
Vendor Name
Vendor Location
Pay_Reference_Number
Pay_date
Purchase Order Detals
Etcetra....

What i am really after is a schematic representation diagram and
explanation for a typical accounts payable and receivable database
design, showing how the tables relate to each other.

Thanks,

pago
 
Ad

Advertisements

G

Golden California Girls

i am talking about the database designs and relationships for the
tables.

thanks,

pago
he wants to reverse engineer the software.

my suggestion to him -- get the SDK
 
L

L

The accounts payable database, for example, have the following tables:

Purchase order:
Purchase order number
Order nbr
Purchase order type
Payable entity
Customer id
Vendor id
Vendor location
Buyer id
Etcetra....

Payment:
Payment method
Pay_reference number
Pay_date
Vendor Id
Vendor Name
Vendor_Address
Bank Account
Pay amount
Journal Id
Etcetra....

Payment request line:
Vendor ID
Vendor Name
Vendor Location
Pay_Reference_Number
Pay_date
Purchase Order Detals
Etcetra....

What i am really after is a schematic representation diagram and
explanation for a typical accounts payable and receivable database
design, showing how the tables relate to each other.
Heh, you have mistaken the nature of this newsgroup. The common denominator
is that most have purchased and used the software.

While database analysis and theory made for an interesting course when I was
in college some thirty years ago, I've found little practical use for it
when using QB - other than some glimmer of an idea as to why certain
proposed features might never be implemented.

QB does have a free SDK - software developers kit.
http://developer.intuit.com/
I don't remember just how explicit the documentation was.

There are also forums dedicated to the use of the SDK.
http://idnforums.intuit.com/
It could be that someone there has an inkling of the QB database table
structures and relationships.

It is also highly likely that a schematic diagram such as the one you desire
is considered proprietary by Intuit, and might not be available.
 
Ad

Advertisements

A

anotherpiece

This information would be highly useful if one wanted to develop any
kind of reporting utilizing the qodbc data. It does not seem like a
wild question at all. The table structures you see coming out of the
qodbc is not readily usable, to say the least. No debits and credits,
no "transaction list" as such and a whole lot of useful garbage. To be
able to link payment with payment details and the affected invoices
would be a minor first absolutely necessary step to developing an open
invoice report for instance. A table relationship diagram would indeed
be helpful. I'll be scouring the sdk site too.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top