Results 1 to 5 of 5
  1. #1
    2 Star Lounger
    Join Date
    Nov 2002
    Location
    Mt. Olive, North Carolina, USA
    Posts
    170
    Thanks
    8
    Thanked 0 Times in 0 Posts

    saving history (97)

    What is the best way to save history? Rename the tables and start with empty tables, or rename the database, or get a 250g hard drive and keep all the records in the tables? <img src=/S/scratch.gif border=0 alt=scratch width=25 height=29> Thanks in advance.

  2. #2
    3 Star Lounger
    Join Date
    Dec 2001
    Location
    Nevada, USA
    Posts
    207
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: saving history (97)

    I was faced with this task several months ago. I ended up setting up a separate mdb file that contains tables corresponding to the production tables from which data was to be archived. I added one field to the history table layout containing the date on which the data is archived. I then wrote VBA code to copy data older than 60 days (that was the client's parameter) to the history tables and then delete those records from the production tables. That code is triggered on a schedule (basically every Monday - it's a restaurant application and Mondays are slow days).

    This scheme has been in production for almost two months and it is working nicely.

    HTH.
    Carol W.

  3. #3
    2 Star Lounger
    Join Date
    Mar 2001
    Location
    Emerald Beach, New South Wales, Australia
    Posts
    126
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: saving history (97)

    What is the best way to save history? Rename the tables and start with empty tables, or rename the database, or get a 250g hard drive and keep all the records in the tables?

    Do you need the archived records to be accessible on demand or is the user prepared to take a few extra steps to retrieve old data?

    I've used an archive table to speed up performance in current data but to allow instant access to archived data. I've use a blank data model for the creation of new data sets with old models being available on the hard drive for 3 months at which point the user burnt the old models on CD for access if required. I've used a blank data model for data backup and used the winzip command line to zip or unzip archived data on demand.

    Post more details relating to your circumstances and what you need to achieve.

  4. #4
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: saving history (97)

    You need to define "history" and give more details of what you're trying to accomplish. If you mean an archive of old data, that's not quite the same thing as history in the sense of an audit trail or a series of data snapshots. Give us more detail.
    Charlotte

  5. #5
    2 Star Lounger
    Join Date
    Nov 2002
    Location
    Mt. Olive, North Carolina, USA
    Posts
    170
    Thanks
    8
    Thanked 0 Times in 0 Posts

    Re: saving history (97)

    Hi all -
    We save job card history for 12 months, a costbook for all the models of product we make that changes once a year, a standard cost file of purchased material that changes once a year, and history of purchase orders. We use the history of job cards and purchase orders to come up with the new standard cost once a year. When we cost our inventory once a year we use last year standards, this year standards, and next years standards. Also purchasing would want to be able to go back to see the history of purchases for any given item.
    Thanks for everyones help.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •