Date not being automatically entered

[FBrnstrmr]

This should be a simple thing but, I have 2 fields into which I wish to place
dates on a form and have them put into the table. They are actually related
but I just want to track them separately. One is the date I create the new
record (=NOW())
and the other is 31 days later. I have absolutely duplicated the entry to
default to =NOW() for the first one a default to =NOW() + 31 for the second.
The starnge thing is that the second one does show 31 days from today, but
the first won't show anything until I try to enter data into another control
and I then get an error stating that the date field must be filled (as I told
it to be) when I click to close the error screen the proper date shows up
where it is supposed to. I have compared the table field definitions as well
as the control properties and they are duplicates except foe the + 31 as
required. Any one have a suggestion, please?
Thanks very much in advance. -Fred

 

[Daniel Pineault]

1. Instead of =Now(), I'd use =Date()
2. Instead of =Now()+31 you need to use the DateAdd function. So try
something like =DateAdd("d",31,Date())
--
Hope this helps,

Daniel Pineault
http://www.cardaconsultants.com/
For Access Tips and Examples: http://www.devhut.net
Please rate this post using the vote buttons if it was helpful.

 

[FBrnstrmr]

Thanks Daniel,
I tried that but there is something else going on which is inexplicable.
There is no apparent reason why the Now, or the Date either for that matter,
won't show up
when the the Now + 31 and the Date + 31 do show up. Any ideas what might
cause a default value to not show. Thanks.
-Fred

 

[Fred]

I don't know the answer but a couple notes and questions that might help sort
it out or narrow it down:

- Make sure you are working directly in the table (when troubleshooting) to
make sure that nothing else is complicating things

- Maybe some other stuff you have in that settings for that field is
interfering. You might narrow that down by making a fresh new little
experimental table and trying just this.

- Your error screen is for enforcing a criteria that you told it to. I
can't see where data entry rules are useful/ necessary for a field that is
automatically loaded. Does eliminating that rule solve your problem?

- Your description of when these is happening seems two steps late in
timing. In normal table views, the defaults are "in the fields" for the
future new record even before it has actually become a record, i.e. at the
moment that you created the "previous" record by entering data into a
non-default field.