[AccessD] Tracking Changes in the Year 2004, Almost 2005

Hi 65

Sounds like Inner Join the two tables, compare each set of fields, and
write out to the track table any record where at least one set of fields
doesn't match.
Then, using another query, append to the track table new records not
found in the *bible*.
The track table could hold a date/time field with default value of
Date.

/gustav

>>> cyx5 at cdc.gov 30-12-2004 19:06:45 >>>
My base table is named Parts.  This is the bible as to part numbers,
descriptions, etc for manufacturers.  The manufacturer submits new
"assemblies" comprised of parts.  If the parts in the new assembly are
in the existing *bible* parts and for instance, the description
changes,
I need an audit table of the parts table showing the part number with
its original description, the new description and of course changed by
and when.

The new assemblies table changes as the manufacturer submits new
products for approval.

-----Original Message-----
From: accessd-bounces at databaseadvisors.com 
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Gustav
Brock
Sent: Thursday, December 30, 2004 12:54 PM
To: accessd at databaseadvisors.com 
Subject: Re: [AccessD] Tracking Changes in the Year 2004, Almost 2005


Hi 65

What is the problem?

/gustav

>>> cyx5 at cdc.gov 30-12-2004 18:38:10 >>>
OK, so I am losing my mind.  I have a QUERY that I am going to run to
update the records in my base table with records from my changes
table.
I want to track which fields were changed from and to.  Every example
I pull is form based and won't run because SOMEBODY sent me an Access
95
example.  Some of you weren't even born in 95.   Aughghghgh!    Any
help is appreciated, as usual.