Getting #NAME? in form

BroncoMarc

Registered User.
Local time
Today, 10:16
Joined
Apr 4, 2002
Messages
43
I'm working with a database I inherited. Most tables are on an SQL server. I need to add on to a form, so I had more fields added to the main table on the SQL server.

The form is based on a query, so next I went to the query and added the fields that I had added to the table. If I run the query by itself it works and I can see the values in those new fields.

Then I went to the form and added the fields from the query. All the new fields I added say #NAME? when I run it. I even used the field chooser in the form and added my new fields that way.. They still all come out as #NAME?

Any ides?


On another note... All the tables in this database are static.. The dynamic data is all kept on an SQL server. This mdb file still grows 2-3 megs a week! Is there anything I can do about that other than compacting the database every once in awhile?

Thanks,
- Marc
 
BroncoMarc said:
This mdb file still grows 2-3 megs a week! Is there anything I can do about that other than compacting the database every once in awhile?

Do you have a lot of graphics?
 
Nope... There are no graphics.

- Marc
 
A lot of queries created on the fly?
 
What do you mean by creating querys on the fly? I've only delt with simple querys, and since I inherited this database, there may be.


Any ideas on the #NAME? showing up in the form? I need to get that problem solved quick so I can put this form update into production.

Thanks,
- Marc
 
I just discovered something else.. I created a new form and added the query fields that were giving me the #NAME?. On the new form it worked.

Next I tried copying the working fields from the new form to the form I'm working on.. It worked, but now when I open the form it give me the error "Can't find the field "Forms" refered to in your expression." then it goes into the form and it works.

I'd appreciate any help...

- Marc
 
When you add columns to tables, they are not automatically added to queries. You need to add the new fields to the form's recordsource query.

If you are deleting the current table contents and importing new data that would account for your db bloat. The other major contributor to bloat is dynamic SQL. That is SQL created in code or used as the recordsource for forms/reports. Dynamic SQL is ALL SQL except that in querydef's.
 

Users who are viewing this thread

Back
Top Bottom