Subject | Re: [ib-support] Thoughts about handling historic data |
---|---|
Author | Woody |
Post date | 2002-02-25T21:46:54Z |
From: "David Husarik" <davidhusarik@...>
fiscal year. When you start a new fiscal year, it creates a new fiscal
archive database and transfers all closed information from the current
archive to the fiscal archive. Then it clears out the current archive to
continue with the new year. This way, the program always works with the main
data and the current archive. Then, if they need to view a fiscal archive,
they select a menu option which let's them pick the one they want to work
with. The program then essentially points the archive database component to
the fiscal file and everything is the same for viewing the archive records.
This seems to work well for my situation but may or may not be a solution
for others. I would think that a lot depends on the design of the data and
how things are related between current and past information.
HTH
Woody
> Hi Group:I start with 2 databases, the main one and the current archive based on the
>
> I am using interbase 6.02, ib objects and delphi.
> I am wondering what the database wizards think about
> the method of handling historic data that needs to be
> referenced. Would it be better to keep this data in
> separate database files opening these files only the
> need arises. Or would you be better off keep the data
> in the original database that captured it in tables
> specifically geared to select and reference. I don't
> know which way to go. Any thoughts are greatly
> appreciated.
>
fiscal year. When you start a new fiscal year, it creates a new fiscal
archive database and transfers all closed information from the current
archive to the fiscal archive. Then it clears out the current archive to
continue with the new year. This way, the program always works with the main
data and the current archive. Then, if they need to view a fiscal archive,
they select a menu option which let's them pick the one they want to work
with. The program then essentially points the archive database component to
the fiscal file and everything is the same for viewing the archive records.
This seems to work well for my situation but may or may not be a solution
for others. I would think that a lot depends on the design of the data and
how things are related between current and past information.
HTH
Woody