Saving prior information of a field when entering new

J

Jeff C

I routinely update a "date field" in my database using a form for data entry
and have wanted to have a way to automatically save the prior information
(prior date) but have never found a way to do this..Does anyone have an
answer they can explain? I am not a visual basic person at all. Each record
may end up having 10 to 20 prior dates in this field eventually. Thank you
 
L

Lynn Trapp

Let me ask some questions that I hope you have already asked and answered,
"Why do you want to save previous dates?" "Do you only want to store the
previous dates or do you also want to store all the information in a record
when it is updated?"

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm


Jeff C said:
I routinely update a "date field" in my database using a form for data entry
and have wanted to have a way to automatically save the prior information
(prior date) but have never found a way to do this..Does anyone have an
answer they can explain? I am not a visual basic person at all. Each record
may end up having 10 to 20 prior dates in this field eventually. Thank
Click to expand...
you
 
R

Rick B

Do a search. "Timestamps" and "audit trails" are discussed on here often.
There are many sample databases out there that do this.


Rick B


Jeff C said:
I routinely update a "date field" in my database using a form for data entry
and have wanted to have a way to automatically save the prior information
(prior date) but have never found a way to do this..Does anyone have an
answer they can explain? I am not a visual basic person at all. Each record
may end up having 10 to 20 prior dates in this field eventually. Thank
Click to expand...
you
 
J

Jeff C

The "Current Date" is part of the record, as is the previous current dates.
Ideally I would create a form including all the previous dates including the
current date. I am not creating an audit trail as such...but the concept may
be the same and just above my head.
 
L

Lynn Trapp

What you are wanting doesn't sound like a typical audit trail process. In
that kind of situation you would have something like a LastUpdateDate and
enter the current date in that field any time a record was changed. It
sounds like what you are asking for is a variable number of dates, each one
successively storing the latest date that a record was updated. The only way
to do that is to have a child table into which you would insert a new record
with a date equal to the previous update date in the parent table. Does that
sound like what you want? I'm still not sure WHY you want to do this.
 
Top