View Single Post
  #13  
Old April 9th, 2010, 08:25 PM posted to microsoft.public.access.tablesdbdesign
hollyylloh
external usenet poster
 
Posts: 18
Default Interested in thoughts on keeping the integrity of historical

Thank you Fred I think you understand my question.

Let's say I am storing invoices that have historical significance and need
to be stored as they were originally derived and printed. Yes, I understand
how relational databases pull the information from the various source tables
at the time of printing and derive the printed invoice. And thus, if I change
the address, all invoices show the new address even on old invoices. This is
precisely the question: What is the best way to ensure the original invoice
transaction is stored as it was originally derived.

Are you suggesting that I create a separate table, for storage purposes,
that holds all the derived data from the various tables in a single table? Or
did you have something else in mind?

The ultimate goal is to retain the historical data while maintaining a very
simple user interface that hides any and all complexity of the design.



"Fred" wrote:

Hello hollyylloh,

I guess I would say it this way. You really haven't told us what your exact
needs are for storing historical data. If your answer is "everything", such
is a big task, and probalby broader than needed.

In my response I was trying to "read between the lines" and guess at the
answer that you didn't give us. You described a very common need/ problem
which is that most Access db's that handle "invoicing" don't treat invoices
as entities to be stored. They treat it as something that is "derived" from
other data (only) at the time of printing. This cause the type of problems
that you describe. You want to look at an old invoice as sent, and
sometimes it no longer possible to do so. Because some of the data has
changed.

If that is the issue, and if it is enough of a problem to be worth some
extra complexity to solve, that would be to consider an invoice to be an
item(entity) that is created and stored (separately from the data that it
was derived from) at the time of invoicing.