Query fields are automatically and incorrectly renamed after updat

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have a problem with a select query in which the names of certain calculated
fields are changed after the query has been updated by an update query. The
change involves the removal of a space in the field name, for example, the
calculated field name “SiH4_1 (mol/min)†becomes “SiH4_1(mol/min)â€.
Subsequent data entries with forms based on this query do not recognize the
calculated field without the space. This requires me to correct all the
fields in the underlying query by re-inserting the space. The database was
built using Access2000 and this problem only arises when I run the database
with our newer version, Access2003.
If anyone knows of a permanent fix, it would be greatly appreciated.
Thanks.
 
1. Never uses any special characters, including spaces, in a field, table,
query, report, form, or module name. Just the 123s and ABCs. The underscore (
_ ) is the only exception. If you want to see something in a report or form
with special characters, do it on a label. Special characters can reek havoc
in code.

2. Go to Tools, Options, General Tab and turn off Name Autocorrect on all of
your databases. IMHO it's a piece of do-do and the cause of many problems.
While there turn off Compact on Close if enabled. You'll be glad that you did.
 
I strongly advise against using spaces or any special characters in field
names. It can cause all kinds of problems over and above those that you
mentioned.
I'd spend the time eliminating the spaces and changing everywhere the
columns are referred to.

Dorian
 
Your suggestion initially did not work, but when I converted the database to
a 2003 format from its original 2000 format, the problem has not reoccurred.
If I create another database in the future I will make sure not to include
any special characters. Thanks very much, Jerry.
 
I used Jerry's suggestion (above) and initially it did not work, but when I
converted the database to a 2003 format from its original 2000 format, the
problem has not reoccurred. If I create another database in the future I
will make sure not to include any special characters. Thanks very much,
Dorian.
 
Back
Top