#Name? Error

H

Howard

Access 2000
Runs on a network
Split front-end/back-end

We have a form with a text box containing a Trim expression(=Trim...). On
one computer only, we are getting a #Name? error on that text box. It appears
that the library references are okay. What could possibly be causing this
error on this one computer.
We think it might be a problem with the computer itself since it sat idle
for several months waiting for a new hire. Maybe it didn't get an upgrade of
some kind.
Thanks,
Howard
 
M

Mike Labosh

We have a form with a text box containing a Trim expression(=Trim...). On
one computer only, we are getting a #Name? error on that text box. It appears
that the library references are okay. What could possibly be causing this
error on this one computer.
We think it might be a problem with the computer itself since it sat idle
for several months waiting for a new hire. Maybe it didn't get an upgrade of
some kind.
Click to expand...

The #Name? you're seeing occurs when a data binding is wrong.

Since the computer was left alone for several months, it might have an older
version of the front end database, and maybe that form's control has its
control source set to something that has been renamed or no longer exists.
--
Peace & happy computing,

Mike Labosh, MCSD

"Mr. McKittrick, after very careful consideration, I have
come to the conclusion that this new system SUCKS!"
~~ General Barringer ~~
 
J

John Vinson

Access 2000
Runs on a network
Split front-end/back-end

We have a form with a text box containing a Trim expression(=Trim...). On
one computer only, we are getting a #Name? error on that text box. It appears
that the library references are okay. What could possibly be causing this
error on this one computer.
We think it might be a problem with the computer itself since it sat idle
for several months waiting for a new hire. Maybe it didn't get an upgrade of
some kind.
Thanks,
Howard
Click to expand...

It's NOT necessary to reinstall Office to fix this!

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.


John W. Vinson[MVP]
 
T

Tom Wickerath

Hi Howard,

I think Mike is right on the money with his suggestion.

Troubleshooting Tips for Error Values
http://support.microsoft.com/?id=209132


Tom
________________________________


Mike,
Thanks for your reply. The IT guy is here and is going to reinstall Office
on that computer. Hope that fixes it.
HF

________________________________



We have a form with a text box containing a Trim expression(=Trim...).
On one computer only, we are getting a #Name? error on that text box.
It appears that the library references are okay. What could possibly be
causing this error on this one computer.
We think it might be a problem with the computer itself since it sat idle
for several months waiting for a new hire. Maybe it didn't get an upgrade
of some kind.
Click to expand...

The #Name? you're seeing occurs when a data binding is wrong.

Since the computer was left alone for several months, it might have an older
version of the front end database, and maybe that form's control has its
control source set to something that has been renamed or no longer exists.
--
Peace & happy computing,

Mike Labosh, MCSD

"Mr. McKittrick, after very careful consideration, I have
come to the conclusion that this new system SUCKS!"
~~ General Barringer ~~

________________________________


Access 2000
Runs on a network
Split front-end/back-end

We have a form with a text box containing a Trim expression(=Trim...). On
one computer only, we are getting a #Name? error on that text box. It appears
that the library references are okay. What could possibly be causing this
error on this one computer.
We think it might be a problem with the computer itself since it sat idle
for several months waiting for a new hire. Maybe it didn't get an upgrade of
some kind.
Thanks,
Howard
 
Top