Calculations return "#Name?"

[Guest]

I have created a form wherein I created some fields to return the result of
simple expressions... for example, =[Departure]-[Arrival] should return the
length of stay. In all, I have 13 fields that are calculated. All of the
fields are coming from the same table. Yesterday, all of these fields
calculated correctly. Today, I added a few more fields to the original table,
the query and the form. All of a sudden, every field that is a calculated
value returns '#Name?'. The new fields added today have nothing to do with
the calculated fields. Can someone help me figure out what happened? It's not
a spelling issue. I imagine that somehow, the calculated fields have lost
their association with the original table. I've even tried using the
Expression Builder, thinking that selecting the field name would restore the
association, but to no avail. Please help!! Thanks! (BTW - Access 2007 Beta)

 

[Guest]

Make sure that non of the text boxes shares a name in common with an existing
field name. The easiest method would be to prefix the names of each text box
with lowercase "txt". For example, if you have a text box named "Departure",
change it's name to txtDeparture.


Tom Wickerath
Microsoft Access MVP

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________

 

[Guest]

Hi Brian

One (or more) of the field names used on the form's fields is not the same
as that in the query that the form is based on. Sorry to say that you will
need to go through each one until you find it. Can I suggest you start with
the new calculated fields you placed on the form today

Hope this helps

--
Wayne
Manchester, England.
Enjoy whatever it is you do
Scusate,ma il mio Inglese fa schiffo
Percio se non ci siamo capiti, mi mandate un
messagio e provero di spiegarmi meglio.

 

[Guest]

For an unknown reason, the fields did become dissociated. I went into the
form design view, selected properties, and choose the table in the "Record
Source" field. Even though it was the same table (query actually), all worked
fine after re-selecting it. Hope it helps someone else who may encounter the
same thing. Thanks to all who replied.

 

[Guest]

Hi Brian,

I have seen that lost recordset sympton once before, when importing a form
from one database to another, but not within the same database. In my case,
it happened when I sent an updated form to another user. Instead of sending
the entire front-end database, which was rather large because of embedded
images that the user wanted to retain, I simply imported a re-worked form
into a new database and sent that to him. I instructed the person I was
helping to import the form into his copy of the FE database. He reported the
same #Name errors. I investigated the situation by deleting the reworked form
from my copy of the DB, and importing it from the saved copy of the message I
had sent to him. Sure enough, I had the same #Name error, which was only
cleared up by re-selecting the recordsource.


Tom Wickerath
Microsoft Access MVP

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________