Suggestions for creating a set of audit trail tables in database
- From: "SarahEmmm" <sarah.mould@xxxxxxxxx>
- Date: 12 Feb 2007 09:06:16 -0800
I'm going to ask here, since I'm using ADO, but this really is quite a
general question:
I want to create a sequence of audit tables within my Access database
(so I can prove what the user altered and when).
Amended data is associated with a start and end date - its possible
that the user may specify overlapping dates if they entered a wrong
date, so the date sequence is not necessarily contiguous.
In addition, I don't want to end up with hundreds of ancient audit
tables. Ideally, they will be deleted if they are over a year old.
My first thought is to give the tables names which incorporate the
associated dates, eg
Audit20070101to20070130
Audit20070101to20070131
but that does seem a bit longwinded. The other option seems to be to
create a straight sequential number, and to save the dates within the
table, eg
Audit07 <--- contains Start Date 01/01/2007, End Date 30/01/2007
Audit08 <--- contains Start Date 01/01/2007, End Date 31/01/2007
Does anyone have a better idea? I want to make it easy for a
technician to review the tables in Access and know what they are
looking at, while also (hopefully) making it easy to decide when a
table is over a year old and can be deleted.
Many thanks for your input...
.
- Prev by Date: Re: Runtime error '3706'
- Next by Date: Re: Runtime error '3706'
- Previous by thread: Re: Runtime error '3706'
- Next by thread: for clevey: well selected nntp server access - os ar - (1/1)
- Index(es):
Relevant Pages
|