Date() Function just stopped working in Access 2003

Hello,

First time on the Microsoft forums but this one is a stumper and if figured
this would be the best place to get an answer.

I am setting up an Access 2003 DB. I was attempting to set the main form for
data entry to "Data Entry" mode (which I did) but when I did a date field I
had set up with the default value of Date() stopped working. I got the
infamous #Name error. So after trying a great many potential solutions I
noticed something...the Now() function worked just fine. This confused me so
I did some more testing when I attempted to add Date() to tables or in any
other area I always got some sort of error. In fact when I switched off the
"Data Entry" mode on the form I still got #Name (Date() had been working
prior to flipping Data Entry to yes).

So now regardless of where I try to use Date() it doenst work anymore. So I
did some research on the net and found people having this same problem dating
all the way back to 2004. The one thing I never found was a workable fix or
solution. I heard the solution of "Check the Refrences". So im not to clear
on the refrences but if it was working before and I didnt change the
refrences they shouldnt be the cause if it suddenly stopped working. If you
dont change the refrences to begin with they shouldnt change all on there own.

So if anyone has a solution on this one please please help cause this one is
frustrating.

On Fri, 12 Feb 2010 10:21:02 -0800, -Devin-
wrote:

So after trying a great many potential solutions I
noticed something...the Now() function worked just fine.

This appears to be the very common References bug. Open any
module in design view, or open the VBA editor by typing
Ctrl-G. Select Tools... References from the menu. One of the
..DLL files required by Access will probably be marked
MISSING. Uncheck it, recheck it, close and open Access.

If none are MISSING, check any reference; close and open
Access; then uncheck it again. This will force Access to
relink the libraries.

This Date() works, Now() doesn't is a very common symptom.

The other possibility is that you might have a field or a control named Date,
in a table or on a form. Access can get confused about which you mean. If
that's the case, change the fieldname.
--

John W. Vinson [MVP]

You assume that you would have to change something to have the
references-related problem ...

Have you heard of gremlins? ... of cosmic rays? ... of powerline
fluctuations? All of these are potential causes, too.

Open a code module.

Use Tools, References.

Uncheck any you find marked "MISSING". (remember which one(s))

Close the window, then reopen it.

Check the one(s) formerly marked "MISSING".

Close the window and run the Debug, Compile.

Try it now.

Regards

Jeff Boyce
Microsoft Access MVP

--
Disclaimer: This author may have received products and services mentioned
in this post. Mention and/or description of a product or service herein
does not constitute endorsement thereof.

Any code or pseudocode included in this post is offered "as is", with no
guarantee as to suitability.

You can thank the FTC of the USA for making this disclaimer
possible/necessary.

"-Devin-" wrote in message
...
Hello,

First time on the Microsoft forums but this one is a stumper and if
figured
this would be the best place to get an answer.

I am setting up an Access 2003 DB. I was attempting to set the main form
for
data entry to "Data Entry" mode (which I did) but when I did a date field
I
had set up with the default value of Date() stopped working. I got the
infamous #Name error. So after trying a great many potential solutions I
noticed something...the Now() function worked just fine. This confused me
so
I did some more testing when I attempted to add Date() to tables or in any
other area I always got some sort of error. In fact when I switched off
the
"Data Entry" mode on the form I still got #Name (Date() had been working
prior to flipping Data Entry to yes).

So now regardless of where I try to use Date() it doenst work anymore. So
I
did some research on the net and found people having this same problem
dating
all the way back to 2004. The one thing I never found was a workable fix
or
solution. I heard the solution of "Check the Refrences". So im not to
clear
on the refrences but if it was working before and I didnt change the
refrences they shouldnt be the cause if it suddenly stopped working. If
you
dont change the refrences to begin with they shouldnt change all on there
own.

So if anyone has a solution on this one please please help cause this one
is
frustrating.