[AccessD] Watching data

Gustav Brock gustav at cactus.dk
Sat Feb 28 06:13:38 CST 2004


Hi John

I see. Then you could add a field with the original CRC value of the
address. If the address is changed, a CRC check will fail.

/gustav


> Well... the data isn't normalized to that extent, i.e. I don't have an
> "Address table".  A claimant has a single address, and that is embedded
> directly in the Claimant table.  Thus a timestamp would only tell me that
> the claimant table had changed, not that the address portion of the table
> had changed.  Maybe she got married and changed her name?  The Date of Birth
> was corrected?  The name was mis-spelled and the mis-spelling was corrected?

> John W. Colby
> www.ColbyConsulting.com

> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Gustav Brock
> Sent: Saturday, February 28, 2004 4:35 AM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] Watching data


> Hi John

> Wouldn't it be much easier to add timestamps and track these? If the
> timestamp of an address is newer than that recorded for the case,
> "something else" has changed the address.

> /gustav


>> I need a system for watching specific data fields in specific tables for
>> changes.  For example, if the Policy holder address changes, the claimant
>> address changes, the Payment location (address) changes etc.  If ANY of
>> these change then I need to gather the information and at the end of the day
>> email a report to the client (the insurance company) spelling out the
>> changes, what object the fields belonged to (Claimant, Policy Holder etc.).




More information about the AccessD mailing list