#Name? error

I know that #Name? means that Access doesn't know what field I'm referring to
- however I get this error "randomly" after I have been in design view. I can
close/reopen the db and the error may be gone. I can fix it by going into the
query upon which the form is base, click in the query (make no changes), save
it and the error is gone. I can save the DB, but then it comes back again
later - sometimes the very next time I open, sometimes not.

Specifically I am getting the error on any/every calculated text field on a
form such as a concatenation of first and last name or a field that puts
year, make, model all on one line.

By the way all of these fields are on the form independently of the
calculated field and I have checked spelling, etc. As I said they really
work, but sometimes they don't.

Why don't they ALWAYS work??

Hi AllYourSpam,
you can get errors like this if you have Name Autocorrect Turned On.
It you have it on, turn if off, do a backup, then compact and repair and see
if the errors go away.


Jeanette Cunningham MS Access MVP -- Melbourne Victoria Australia


"AllYourSpam" wrote in message
...
I know that #Name? means that Access doesn't know what field I'm referring
to
- however I get this error "randomly" after I have been in design view. I
can
close/reopen the db and the error may be gone. I can fix it by going into
the
query upon which the form is base, click in the query (make no changes),
save
it and the error is gone. I can save the DB, but then it comes back again
later - sometimes the very next time I open, sometimes not.

Specifically I am getting the error on any/every calculated text field on
a
form such as a concatenation of first and last name or a field that puts
year, make, model all on one line.

By the way all of these fields are on the form independently of the
calculated field and I have checked spelling, etc. As I said they really
work, but sometimes they don't.

Why don't they ALWAYS work??

If it were only that easy. No, my Name Autocorrect is not on. Thanks to the
many experts on this, and other forum, I have gone through all the steps to
correct all the errors, bugs etc. that MS refuses to correct in a timely
manner and I always start a new database from a "template" I have developed.
A-number-one on the list is to have the Name Autocorrect turned off.

Access can be so great and powerful, yet SO frustrating at times.

Thanks for your thoughtful idea. I do appreciate the help that is given here
- in all the posts.

Here is another question:
Recently, I have noticed that the Access forum has been really slow to load
(sometimes the threads don't load) and the reply link to bring me back to
this post didn't work, I did a search for my subject line, it didn't bring up
my post so I had to go back into the daily post and find it.

Is anyone else having these issues ... or is it always just me??? :-)

"Jeanette Cunningham" wrote:

Hi AllYourSpam,
you can get errors like this if you have Name Autocorrect Turned On.
It you have it on, turn if off, do a backup, then compact and repair and see
if the errors go away.


Jeanette Cunningham MS Access MVP -- Melbourne Victoria Australia


"AllYourSpam" wrote in message
...
I know that #Name? means that Access doesn't know what field I'm referring
to
- however I get this error "randomly" after I have been in design view. I
can
close/reopen the db and the error may be gone. I can fix it by going into
the
query upon which the form is base, click in the query (make no changes),
save
it and the error is gone. I can save the DB, but then it comes back again
later - sometimes the very next time I open, sometimes not.

Specifically I am getting the error on any/every calculated text field on
a
form such as a concatenation of first and last name or a field that puts
year, make, model all on one line.

By the way all of these fields are on the form independently of the
calculated field and I have checked spelling, etc. As I said they really
work, but sometimes they don't.

Why don't they ALWAYS work??

Have you checked for the correct references for this database?
Have you done a compact and repair, or a decompile followed by compact and
repair?
What happens if you create another database as a test, keep it simple, use
only enough tables and queries to build this one form with the #Name error.

Jeanette Cunningham MS Access MVP -- Melbourne Victoria Australia


"AllYourSpam" wrote in message
news
If it were only that easy. No, my Name Autocorrect is not on. Thanks to
the
many experts on this, and other forum, I have gone through all the steps
to
correct all the errors, bugs etc. that MS refuses to correct in a timely
manner and I always start a new database from a "template" I have
developed.
A-number-one on the list is to have the Name Autocorrect turned off.

Access can be so great and powerful, yet SO frustrating at times.

Thanks for your thoughtful idea. I do appreciate the help that is given
here
- in all the posts.

Here is another question:
Recently, I have noticed that the Access forum has been really slow to
load
(sometimes the threads don't load) and the reply link to bring me back to
this post didn't work, I did a search for my subject line, it didn't bring
up
my post so I had to go back into the daily post and find it.

Is anyone else having these issues ... or is it always just me??? :-)

"Jeanette Cunningham" wrote:

Hi AllYourSpam,
you can get errors like this if you have Name Autocorrect Turned On.
It you have it on, turn if off, do a backup, then compact and repair and
see
if the errors go away.


Jeanette Cunningham MS Access MVP -- Melbourne Victoria Australia


"AllYourSpam" wrote in message
...
I know that #Name? means that Access doesn't know what field I'm
referring
to
- however I get this error "randomly" after I have been in design view.
I
can
close/reopen the db and the error may be gone. I can fix it by going
into
the
query upon which the form is base, click in the query (make no
changes),
save
it and the error is gone. I can save the DB, but then it comes back
again
later - sometimes the very next time I open, sometimes not.

Specifically I am getting the error on any/every calculated text field
on
a
form such as a concatenation of first and last name or a field that
puts
year, make, model all on one line.

By the way all of these fields are on the form independently of the
calculated field and I have checked spelling, etc. As I said they
really
work, but sometimes they don't.

Why don't they ALWAYS work??