R
Richard
My message of minutes ago, Subject: DLast function was a
bit misleading. I mentioned that my database consists of
records where each new record is the day after the
previous record. I don't want the date info in the
previous record's [DATE] field entered into the next
record's date field - I want the next date information
entered into the new record's [DATE] field. This should
involve a DLast Lookup of the previous record's [DATE]
field and some kind of expression. I did this in a
database numbering system almost like autonumber which
used DLast "VCR" number and added one to it for the next
(new) record's "VCR" number field. Again, this was some
years ago. The next date information is not necessarily
the current date's value (that one I know) since I don't
update every day. I notice that time is Pacific - it is
12:30p here in Florida.
bit misleading. I mentioned that my database consists of
records where each new record is the day after the
previous record. I don't want the date info in the
previous record's [DATE] field entered into the next
record's date field - I want the next date information
entered into the new record's [DATE] field. This should
involve a DLast Lookup of the previous record's [DATE]
field and some kind of expression. I did this in a
database numbering system almost like autonumber which
used DLast "VCR" number and added one to it for the next
(new) record's "VCR" number field. Again, this was some
years ago. The next date information is not necessarily
the current date's value (that one I know) since I don't
update every day. I notice that time is Pacific - it is
12:30p here in Florida.