Name AutoCorrect

[Antonio]

This question sprung from a suggestion "TC" <[email protected]>
gave to me about database security at 4/5/2004 8:31:47 PM
on the Microsoft Security Message Board...as well as
Arvin Meyer, Tom Wickerath, and Tony Toews on this
Message Board...thank you all for your help thus far....

For some time now I have had several forms, two in
particular, that take forever to open. I recently (like
minutes ago) split our database into a front and back
end. The forms that took forever to load, 2 in particular
(one 8 seconds-the other 11 seconds), now take 20 and 35
seconds to load in the Front End of the database. These
forms have tab controls with several sub forms on them.

I was going through the support articles and came across
the Name AutoCorrect can cause forms to load for a long
time. When I deselected all three AutoCorrect options
under the general tab under the Options screen, the forms
loaded in 2 or 3 seconds... much faster and indeed made
me smile.
However, I know its in black and white, right there, but
I am having a hard time understanding their explaination
of the Auto Correct function itself and the fix they
offer.
Specifically:

1. If Name AutoFix is selected under options for a
database, does it check everytime a form(object) is
opend? Is there a draw back to not having it (there are
actually three options..Track AutoCorrect, Perform
AutoCorrect, Log NameAutoCorrect Changes) selected for a
database?

2. The article suggests having a different user with
modify permissions (no one at this point, as the
developing person I only gave myself modify permissions)
open the object...does that mean that the autocorrect
stops checking after the user with modify permissions
first opens the object? When will it start checking
again? What happens after that user opens the object? Do
they have to save something after they open the object?

3. Of the three auto correct options, can one get by with
only 1 or 2 of the options checked off?

4. Does the Auto Correct options need to be used at all
in the Front End of a database? I ask because, as I
understand it, any time I make changes to the database
front end, I need to replace the copy that resides on the
individual terminals (18) with a copy of the newly
changed database.

I know its there in the article...but if its not too much
trouble, could anyone perhaps break down the Auto Correct
function/fix in more generic terms for me?

(Im afraid I am sounding like an idiot...)

Thanks In Advance.

 

[Tom Wickerath]

Hi Antonio,

If Name AutoFix is selected under options for a
database, does it check everytime a form(object) is
opened? Is there a draw back to not having it...

My understanding is that if Access cannot find something, such as a field name, a record source,
a table specified in a query, etc., that it then turns to a so-called "name map" to attempt to
resolve the reference. It does this only if you have Name Autocorrect enabled and an error is
found. Otherwise, it just presents a #Name? error if NameAutocorrect has been disabled. If it
finds everything okay, then no problem....however, if it doesn't find something then you have the
extra time spent attempting to resolve the differences. The only drawback to not having it is
that you can potentially receive an error, but these are usually easy enough for a developer to
spot and correct beforehand.

does that mean that the autocorrect stops checking after
the user with modify permissions first opens the object?

If this user saves the object in design view, then my understanding is that autocorrect will not
be invoked, unless a dependent object, such as a table included in a query is later renamed.

When will it start checking again?

When an error would normally be encountered, but only if Name Autocorrect is enabled.

Do they have to save something after they open the object?

Yes, they need to save the object in design view to update the name map.

3. Of the three auto correct options, can one get by with
only 1 or 2 of the options checked off?

No. I cannot recommend this. A slow form or report just makes you look bad. Wouldn't you rather
see a #Name? error one time, and correct it, instead of not knowing that an error is present and
being corrected for you behind-the-scenes?

4. Does the Auto Correct options need to be used at all
in the Front End of a database?

No. This is one of the first things I disable in new databases. If you start with a good
database design (read: on paper with pencil), and you use naming conventions along the way, you
will have much fewer instances of needing to change the name of a field, table, query, etc. later
on. If you choose to use NameAutocorrect, then make sure to update the name maps, by opening all
objects in design view and saving them, just before you are ready to release your application.
Then disable NameAutocorrect just to be on the safe side.

To update the name map, one needs to open each object in design view and then save it. This is
why you need modify permissions for the object in question. You might want to try a utility that
Michael Kaplan has made available:
http://www.trigeminal.com/lang/1033/utility.asp?ItemID=10#10

I also recommend disabling subdatasheets on tables. See:
ACC2000: Slower Performance on Linked Tables
http://support.microsoft.com/?id=261000
Note: This article applies to Access 2002 and 2003 as well.

These forms have tab controls with several sub forms on them.

In that case, I highly recommend late-binding your subforms. See the following tip for how to
accomplish this:
http://www.fmsinc.com/free/tips.html#accesslatebind


Tom
______________________________________



This question sprung from a suggestion "TC" <[email protected]>
gave to me about database security at 4/5/2004 8:31:47 PM
on the Microsoft Security Message Board...as well as
Arvin Meyer, Tom Wickerath, and Tony Toews on this
Message Board...thank you all for your help thus far....

For some time now I have had several forms, two in
particular, that take forever to open. I recently (like
minutes ago) split our database into a front and back
end. The forms that took forever to load, 2 in particular
(one 8 seconds-the other 11 seconds), now take 20 and 35
seconds to load in the Front End of the database. These
forms have tab controls with several sub forms on them.

I was going through the support articles and came across
the Name AutoCorrect can cause forms to load for a long
time. When I deselected all three AutoCorrect options
under the general tab under the Options screen, the forms
loaded in 2 or 3 seconds... much faster and indeed made
me smile.
However, I know its in black and white, right there, but
I am having a hard time understanding their explaination
of the Auto Correct function itself and the fix they
offer.
Specifically:

1. If Name AutoFix is selected under options for a
database, does it check everytime a form(object) is
opend? Is there a draw back to not having it (there are
actually three options..Track AutoCorrect, Perform
AutoCorrect, Log NameAutoCorrect Changes) selected for a
database?

2. The article suggests having a different user with
modify permissions (no one at this point, as the
developing person I only gave myself modify permissions)
open the object...does that mean that the autocorrect
stops checking after the user with modify permissions
first opens the object? When will it start checking
again? What happens after that user opens the object? Do
they have to save something after they open the object?

3. Of the three auto correct options, can one get by with
only 1 or 2 of the options checked off?

4. Does the Auto Correct options need to be used at all
in the Front End of a database? I ask because, as I
understand it, any time I make changes to the database
front end, I need to replace the copy that resides on the
individual terminals (18) with a copy of the newly
changed database.

I know its there in the article...but if its not too much
trouble, could anyone perhaps break down the Auto Correct
function/fix in more generic terms for me?

(Im afraid I am sounding like an idiot...)

Thanks In Advance.