Archiving various versions of data

[mforema]

Hi Everyone,

I have a database that currently has two types of tables: one type has all of the current data, and the other type has all of the previous, outdated data. I already have command buttons on my form that opens a previous data query, so that the user can view the outdated data if he/she needs to.

However, the database may need to grow to allow a way for users to view various versions of the data. People at my work agree that some type of archiving system needs to be implemented.

Does anyone have suggestions for the best layout for an archived database?

Thanks!

[tdw]

Hi Everyone,

I have a database that currently has two types of tables: one type has all of the current data, and the other type has all of the previous, outdated data. I already have command buttons on my form that opens a previous data query, so that the user can view the outdated data if he/she needs to.

However, the database may need to grow to allow a way for users to view various versions of the data. People at my work agree that some type of archiving system needs to be implemented.

Does anyone have suggestions for the best layout for an archived database?

Thanks!

Do you mean that data referring to a particular thing (product, work order, or whatever) will change over time, but that all previous incarnations have to be kept and accessible as well?

Or do you mean that you want old outdated things that no longer exist to be archived?

[puppydogbuddy]

Do you mean that data referring to a particular thing (product, work order, or whatever) will change over time, but that all previous incarnations have to be kept and accessible as well?

Or do you mean that you want old outdated things that no longer exist to be archived?

The following links contain guidelines for creating and naming the archive tables, appending data to it, and deleting data from the current version.

As an alternative way of archiving, you might consider creating "read only" copies of your existing mdb file, rather than archiving on a transaction basis as described in the links

Archiving records in an Access database
http://office.microsoft.com/en-us/ac...345681033.aspx


Example using an append query for archiving records
http://www.databasedev.co.uk/append_query.html
.

[mforema]

The following links contain guidelines for creating and naming the archive tables, appending data to it, and deleting data from the current version.

As an alternative way of archiving, you might consider creating "read only" copies of your existing mdb file, rather than archiving on a transaction basis as described in the links

Archiving records in an Access database
http://office.microsoft.com/en-us/ac...345681033.aspx


Example using an append query for archiving records
http://www.databasedev.co.uk/append_query.html
.

Thanks! I will test out these ideas.

[mforema]

Do you mean that data referring to a particular thing (product, work order, or whatever) will change over time, but that all previous incarnations have to be kept and accessible as well?

Or do you mean that you want old outdated things that no longer exist to be archived?

In this case, both situations apply. But I think the first question is the best way to view our situation.