Accounting Database

I am not sure if when designing an Accounting Database should there be a
seperate table for Charges and Payments, or rather a single table called
Transactions.

Can anyone comment on Pros and Cons?

Thanks

A good general rule for table design is that you can describe the table in
one sentence without using the word "and". Consider that if each charge can
be associated with an indefinite number of payments then it is best
(essential, really) to keep payments in a separate table linked to the
charges table. In form view Payments would be a subform of Charges, which in
turn could be a subform of Clients (or whatever).

"Gary B" wrote:

I am not sure if when designing an Accounting Database should there be a
seperate table for Charges and Payments, or rather a single table called
Transactions.

Can anyone comment on Pros and Cons?

Thanks

The answer to your question may depend on whether you plan to use Double
Entry accounting or Single Entry accounting. If you need a full fledged
Double Entry accounting application then you will probably be better off by
using separate tables. Single Entry can be handled easily with a single
table.

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm


"Gary B" wrote in message
...
I am not sure if when designing an Accounting Database should there be a
seperate table for Charges and Payments, or rather a single table called
Transactions.

Can anyone comment on Pros and Cons?

Thanks

Why would you want to do Accounting in Access? There are many very good and
simple to use accounting programs and most will integrate with Access for
specific querying and reports.

"Gary B" wrote:

I am not sure if when designing an Accounting Database should there be a
seperate table for Charges and Payments, or rather a single table called
Transactions.

Can anyone comment on Pros and Cons?

Thanks