[AccessD] Recording field changes

David:

If the client wants to see all changes to a record on a field by field bases
then the/each transaction file(s) will have to have a minimum of a complete
copy of each record structure of each table or at least any field that a
user can affect. In addition fields such as time/date and operator will have
to be added to each of the transaction records. There may be ways to handle
different changes but the whole transaction monitoring depends on speed and
any fancy data handling will decrease it. There will be more records in the
transaction file, than the original, though most records will/should be
accessed once.

HTH
Jim

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of David Emerson
Sent: Monday, June 21, 2004 1:44 PM
To: accessd at databaseadvisors.com
Subject: [AccessD] Recording field changes


Group,

I have a client that needs to record all changes to the data on a field by
field basis (they don't want to record whole records if there is a change -
just the fields that changed (old and new values)).  My initial though is
to put code in every field that records the value on entry, compares this
on exit and records the change if they values are different.

Because there are several hundred fields involved I was wondering if there
was any easy way of doing the job without adding code to every field.

Regards

David Emerson
Dalyn Software Ltd
25 Cunliffe St, Churton Park
Wellington, New Zealand
Ph/Fax (04) 478-7456
Mobile 027-280-9348

--
_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com