Name AutoCorrect Does Not Repair Query Field/Table Names

View products that this article applies to.

Symptoms

When you have the Name AutoCorrect feature enabled, and you make changes to a query's record source, such as changing a table name, a query name, or a field name, and you then run the query, the query may:

Prompt for the old field name value.
Return unexpected results.
Display the following error message:
"The Microsoft JET Database Engine could not find the input table or query '<Table or Query Name>'. Make sure it exists and the name is spelled correctly."

↑ Back to the top

Cause

These symptoms may be caused by one or more of the following:

The query was built by the query wizard and either a field name or table name was changed.

-or-

The query is an action query, such as an update or append query, and the field that was changed is in an output column.

-or-

The query contains a table with a large number of fields (more than 125 fields depending on the length of the field names) and the field name that was changed is one of the last fields.

-or-

The query is based on a query that has a field with an alias and the alias was changed.

-or-

The query is based on a table in which the first field is renamed and a second field is renamed to the name of the first field.

↑ Back to the top