I changed the name of a field in one of my tables (before you all scold me,
don't, I won't ever, ever, ever do it again!) and then changed all of the
references to it on the only form that uses that particular field. I change
it in the underlying query and all of the code for that form. Problem is,
MSAccess doesn't agree. When I open the form it pops up the box to Enter
Parameter Value for and includes the old field name. Like I said, I searched
the code behind the form for references to the old field name to no avail.
searched all of the queries that use that table. I even ran the Access
analyzer on that form and then searched the document for the old field name
and came up empty. Is there any way to force Access to tell me why it is
attempting to get this value, i.e. what triggers it. Something similar to
using breakpoints in the code builder?

If it makes a difference. I can put anything I want into the pop up box or
cancel it and it does nothing to affect the form (nothing that I can see
anyway!)

Jimmy

Jimmy wrote:

I changed the name of a field in one of my tables (before you all scold me,
don't, I won't ever, ever, ever do it again!) and then changed all of the
references to it on the only form that uses that particular field.

You may have references that you don't see immediately, e.g control sources
in forms, conditional formatting etc.

Try this procedure, sometimes it works:

1. Give the field the original name in the table again.
2. In Tools - Options - General - Name AutoCorrect put a tick
against Track name AutoCorrect info and Perform name AutoCorrect.
3. Give the field the new name again. (This should modify all
references visible to Access automatically).
4. Modify references not visible to Access manually. This is
mainly in VBA code.

Another option would be to save the object (Application.SaveAsText) and
search with a text editor.

Peter Doering

--
No mails please.

Perfect, worked like a charm. Is this name autocorrect a new feature to A2k
over A97? What a brilliant tool, I will keep it turned on from now on!!!

Jimmy

"Peter Doering" <nospam@doering.orgwrote in message
news:4rupcsFt3lkfU1@mid.individual.net...

Jimmy wrote:
>

>
You may have references that you don't see immediately, e.g control
sources
in forms, conditional formatting etc.
>
Try this procedure, sometimes it works:
>
1. Give the field the original name in the table again.
2. In Tools - Options - General - Name AutoCorrect put a tick
against Track name AutoCorrect info and Perform name AutoCorrect.
3. Give the field the new name again. (This should modify all
references visible to Access automatically).
4. Modify references not visible to Access manually. This is
mainly in VBA code.
>
Another option would be to save the object (Application.SaveAsText) and
search with a text editor.
>
Peter Doering
>
--
No mails please.

"Jimmy" <none@none.comschreef in bericht news:gpq6h.380248$aI2.275357@fe06.news.easynews.co m...

Perfect, worked like a charm. Is this name autocorrect a new feature to A2k
over A97? What a brilliant tool, I will keep it turned on from now on!!!

Hmmm... I would Google for this mis-feature, AKA 'Name Auto Corrupt' option...
Not so brilliant at all !

Arno R

Jimmy wrote:

Perfect, worked like a charm. Is this name autocorrect a new feature to A2k
over A97? What a brilliant tool, I will keep it turned on from now on!!!

Hey, don't get carried away! ;-)

The name autocorrect feature should be switched on when required, i.e.
during development, when changing object or control names. Once the db is
operational it should be off, as it's one of the most common reasons for
performance problems. So don't leave it on when you don't need to.

Peter

--
No mails please.

Oh, then off it goes...until needed!

"Peter Doering" <nospam@doering.orgwrote in message
news:4rv0j0Ftc28aU1@mid.individual.net...

Hey, don't get carried away! ;-)
>
The name autocorrect feature should be switched on when required, i.e.
during development, when changing object or control names. Once the db is
operational it should be off, as it's one of the most common reasons for
performance problems. So don't leave it on when you don't need to.
>

"Jimmy" <none@none.comwrote in message
news:8KL6h.289923$Mn2.193950@fe02.news.easynews.co m...

Oh, then off it goes...until needed!
>
>

It is, without doubt, an absolute last resort when your desperation has
reached epic proportions. This explains why:

http://allenbrowne.com/bug-03.html

Keith.
www.keithwilby.com

Keith Wilby wrote:

It is, without doubt, an absolute last resort when your desperation has
reached epic proportions. This explains why:
>
http://allenbrowne.com/bug-03.html

I've never turned this off and I've never experienced any slowdown,
corruption or other problem relating to it.
I can't remember ever changing field names; perhaps that's why.
Regardless, one of the reasons I am drifting away from Access is MS's
increasing tendency to DO THINGS for the developer or programmer. I
don't want MS to do anything for me and I find it both annoying and
counter-productive when it does.
If MS sincerely wants to improve Access it will replace the woeful and
archaic VBA with something else.

Lyle Fairfield wrote:

If MS sincerely wants to improve Access it will replace the woeful and
archaic VBA with something else.
>

Like what?

..net?