I'm looking for suggestions regarding the archiving of a database. The way the app is now, all of the data they enter is shown on a dbgrid. Now let's say in a year from now they may not want to see data they entered last year, but may on occasion want access to it.
My thought was to include a function which lets them archive data from from a fixed period (ie. calendar year...1999), or let them choose a period. I would then store the database under a different name (ie. 1999.mdb) and recreate the database structure so they would be working with a new and empty DB.
Does anyone have any thoughts or suggestions about this or any other approaches???
My thought was to include a function which lets them archive data from from a fixed period (ie. calendar year...1999), or let them choose a period. I would then store the database under a different name (ie. 1999.mdb) and recreate the database structure so they would be working with a new and empty DB.
Does anyone have any thoughts or suggestions about this or any other approaches???