#Name error on date() and time()

  • Thread starter Thread starter Mike D.
  • Start date Start date
M

Mike D.

I'm sure that this is a common problem to get the #Name,
but I have a slight twist to it.

My database is set to show the current date "date()" on a
form and it works fine.

I tried it on a Windows98 computer and got the #Name in
the field where the date was supposed to be. An error
also popped up on the screen looking for a .dll file.
So, I copied the "srchasst" folder from my WinXP to the
Win98 AND EVERYTHING WORKS!

The above works on about 20 computers, but there's 1
stubborn computer we have that still shows the #Name and
throws you into Visual Basic for fixing. An error
doesn't pop up saying that I'm missing a .dll

Any suggestions?

Thanks,
Mike D.
 
Any time you have an application that works on some workstations but not on
others, the first thing to suspect is a References problem.

This can be caused by differences in either the location or file version of
certain files between the machine where the application was developed, and
where it's being run (or the file missing completely from the target
machine). Such differences are common when new software is installed.

On the machine(s) where it's not working, open any code module (or open the
Debug Window, using Ctrl-G, provided you haven't selected the "keep debug
window on top" option). Select Tools | References from the menu bar. Examine
all of the selected references.

If any of the selected references have "MISSING:" in front of them, unselect
them, and back out of the dialog. If you really need the reference(s) you
just unselected (you can tell by doing a Compile All Modules), go back in
and reselect them.

If none have "MISSING:", select an additional reference at random, back out
of the dialog, then go back in and unselect the reference you just added. If
that doesn't solve the problem, try to unselect as many of the selected
references as you can (Access may not let you unselect them all), back out
of the dialog, then go back in and reselect the references you just
unselected. (NOTE: write down what the references are before you delete
them, because they'll be in a different order when you go back in)

For far more than you could ever want to know about this problem, check out
http://members.rogers.com/douglas.j.steele/AccessReferenceErrors.html
 
Mike,

Access is probably missing some 'References' on your problem
computer(s). Open a code module and then go to
Tools/References and see if any are flagged as missing. If
they are you may be able to find them in the list.

--

Gary Miller
Gary Miller Computer Services
Sisters, OR
________________________
 
Thank you! This fixed my problem!

Mike D.
-----Original Message-----
Any time you have an application that works on some workstations but not on
others, the first thing to suspect is a References problem.

This can be caused by differences in either the location or file version of
certain files between the machine where the application was developed, and
where it's being run (or the file missing completely from the target
machine). Such differences are common when new software is installed.

On the machine(s) where it's not working, open any code module (or open the
Debug Window, using Ctrl-G, provided you haven't selected the "keep debug
window on top" option). Select Tools | References from the menu bar. Examine
all of the selected references.

If any of the selected references have "MISSING:" in front of them, unselect
them, and back out of the dialog. If you really need the reference(s) you
just unselected (you can tell by doing a Compile All Modules), go back in
and reselect them.

If none have "MISSING:", select an additional reference at random, back out
of the dialog, then go back in and unselect the reference you just added. If
that doesn't solve the problem, try to unselect as many of the selected
references as you can (Access may not let you unselect them all), back out
of the dialog, then go back in and reselect the references you just
unselected. (NOTE: write down what the references are before you delete
them, because they'll be in a different order when you go back in)

For far more than you could ever want to know about this problem, check out
http://members.rogers.com/douglas.j.steele/AccessReferenc eErrors.html


--
Doug Steele, Microsoft Access MVP

(No private e-mails, please)






.
Click to expand...
 
Back
Top