Design Pointers/suggestions ???

Hi there

I'm looking for Design Pointers/suggestions NOT code !

I have been assigned to develop an App that would maintain 600+ staff daily log.
This Org. Operates on 3 shifts a day/ 7 days a week/ 365 days a year.
After doing some testing, by the end of the year, my MDB would be around 10+ MB.
AND here is the Q:

How would I handle Monthly/Yearly (Back up/Archiving) since restoring would overwrite the original data ?


Thanx.

Lyla

I help in the creation of a similar system that recorded staff information, work the member of staff had done and how long it took them.

Due to there being a lot of staff in the office the database got quite full.

To remedy this this the archiveing method used so as not to overwrite the old data was to backup the database as e.g

The database would check to see if it was the 1st to the 5th of the month (to allow for weekends and such). I would then work out twhat the previous month was and current year.

I would then create a string Jul00.mdb and use this as the name of the backed up database.