[AccessD] Re: Watching data

John,

One of the ways this is handled in a data warehouse is to just write a 
history record with all of the previous information.  For your report, you 
could show the current data and the previous data.

RObert

At 10:16 AM 2/29/2004 -0600, you wrote:
>From: accessd-bounces at databaseadvisors.com
>[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of John W. Colby
>Sent: Saturday, February 28, 2004 4:04 AM
>To: Access Developers discussion and problem solving
>Subject: RE: [AccessD] Watching data
>
>
>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.).