Propagating Field Name Changes

  • Thread starter Thread starter Chaplain Doug Pruiett
  • Start date Start date
C

Chaplain Doug Pruiett

Access 2002. I recently began redesigning my database
applying more "normal" rules for table design and field
names. I have changed a host of field names from all CAPS
to a mix (LASTNAME becomes LastName, etc.). Queries
automatically seem to update to the latest names.
However, forms, reports, and modules do not. I know that
the forms, reports and modules will still get the data
referencing LASTNAME instead of LastName. However, for
the sake of consistency and sanity, I wish to propagate
the name changes across all objects. Is there an easy way
(easier than going into each form and report and changing
each control by hand)? Thanks for the help.
 
Access 2002. I recently began redesigning my database
applying more "normal" rules for table design and field
names. I have changed a host of field names from all CAPS
to a mix (LASTNAME becomes LastName, etc.). Queries
automatically seem to update to the latest names.
However, forms, reports, and modules do not. I know that
the forms, reports and modules will still get the data
referencing LASTNAME instead of LastName. However, for
the sake of consistency and sanity, I wish to propagate
the name changes across all objects. Is there an easy way
(easier than going into each form and report and changing
each control by hand)? Thanks for the help.
Click to expand...

I'd suggest getting one of the good third-party tools that have been
written for this purpose. I like Speed Ferret myself, but there are
cheaper alternatives:

Free:
http://www3.bc.sympatico.ca/starthere/findandreplace
Find and Replace: http://www.rickworld.com
Speed Ferret: http://www.moshannon.com
Total Access Analyzer: http://www.fmsinc.com
 
I tried the first two Ad-Ins on the list and they did not
accomplish the job. I told them to change all LASTNAME to
LastName. Wherever LASTNAME appears as a control name,
field name, or variable name it still reamined LASTNAME
after the "change." Any further suggestions? Thanks.
 
Another strange phenomenon: although the control (and its
label) have new names LastName and LastName_Label, when I
am in the code editor and type "Me." and search the list
that pops up, these control names do not appear. Instead
LASTNAME appears and LASTNAME_Label appears but not
LastName, even though the properties for the control show
a name and source of LastName. How did this get hosed up?
 
Even when I delete the control on the form and recreate it
with name LastName, when in the code editor me. pops up a
list with LASTNAME as the control name. Any suggestions
why?
 
Do you have anything in AutoCorrect that may be doing this?

Also do you have a function in your database named LASTNAME?
 
Hey Joan, Checked all that stuff. Funny thing:
I "rebuilt" the database by opening a blank database,
importing all tables from the backend, then importing all
other objects. Now all the changes I made (all the CAPS
fields changed to Caps) have taken in the rebuilt version
and there is no longer an issue. Thanks.
 
After six+ hours of manual edits, editing add-ins, etc.
with nothing working, I tried the following:

1. Open blank database.
2. Import all the tables from my backend.
3. Import all the other objects from my front end.

Now all the changes the add-ins and manual tries attempted
are there throughout. LASTNAME has changed to LastName,
FIRSTNAME to FirstName, etc. I guess I did so many dorky
and desperate things (like getting 100 miles down the road
and then changing all the field names!) that I hosed up
the original database. Anyhow, appears that I am on
track.

Lesson learned? Doing steps 1-3 above sometimes works
when you really get things hosed up. I guess that Access
2002 is NOT idiot-proof as demonstrated by me.

Thanks all for your time and effort. God bless.
 
Lesson learned? Doing steps 1-3 above sometimes works
when you really get things hosed up. I guess that Access
2002 is NOT idiot-proof as demonstrated by me.
Click to expand...

It's been amply demonstrated in these groups that Access is not
idiot-proof, nor is it causal-user, superuser, expert or guru-proof!

I hadn't seen this capitalization misfeature; clearly SOMEWHERE in the
undocumented recesses of the database it had a memory of the original
name and wouldn't let it go.

Glad you got it sorted out! and yes - steps 1-3 are becoming a fairly
routine recommendation when people have wierd problems (or even
un-compactable bloating).
 
Back
Top