Prev: How do I break a link to an external database but keep table data?
Next: AutoNumber vs. Natural Primary Keys
From: icccapital on 6 Jan 2010 16:15
I do have an invoices table, are you thinking that there should be the
address for each invoice created or if thre are two addresses a secondary
table that would have invoice id and the address so it is kept like that?
And each period addresses are written to this table as invoices are created?

I was trying to clarify what you said to see if i understood. thanks

"Fred" wrote:

> IMHO you have a fundamental "entity: issue. The invoice, with all of it's
> then-current details, is an entity that you created and need to look back at.
> In that case you would probable need an "invoices" table (probably a pair of
> linked tables, the header information and the detail information.
>
From: Fred on 7 Jan 2010 13:22
First, to clarify, my approach is very different than Jeff's. If the only
thing (that you need to be able to look back on) that will ever change is
the address, then I think that Jeff's way is better.

Then ther is the low tech way of doing what I was saying, which would be to
print and file the invoice.

To do the electronic way of what I was saying, by software or user
practices, you should make sure that an invoice is treated as a one time
event. After that you are only producing COPIES of the invoice.

Then under my way, you would make an "InvoiceHeader" table which has all of
the "once per invoice" data, exactly as printed. (except for items
mathematically calculated form items on the invoice) mathematically
calculated items) And then the same as the above with an "InvoiceItems"
table.



 | 
Pages: 1
Prev: How do I break a link to an external database but keep table data?
Next: AutoNumber vs. Natural Primary Keys