If you rename any object in a database created in MS Access 97 and earlier Access versions, then you are at the risk of breaking various other objects that are dependent on this object. For instance, suppose you have some reports and forms that extract their data through a query, and thus in turn this query is referencing different tables. If you rename this query, then the data extraction process of associated forms and reports will throw erratic results as they are pointing a non-existing query. In this tutorial, we take a look at the common bugs or issues with Name AutoCorrect feature in Access 2000.
To resolve this problem, you have to open every form and each report associated to this query in ‘Design’ view, open the property sheet of object, and after that re-point the ‘RecordSource’ property of every single report and form to this new query. In this way, just for a single change, you have to deploy considerable amount of time and work both.
However, this problem is resolved in Access 2000 and later versions as the Name AutoCorrect feature is added. This feature of Access 2000 and later works to correct side effects of renaming queries, forms, objects, tables, and other controls of Access database. This is how the forms, query, and reports, automatically recognize the new or changed name. Apart from the usability of this feature of MS Access, the Name AutoCorrect feature of MS Access 2000 has some bugs.
Issues with Name AutoCorrect Feature
Issues with ‘queries’:
1. When you use Name AutoCorrect feature of MS Access 2000 for changing the name of a record of a query, like if you have changed the table name, name of a field, or name of the query, and then run the query, then you may experience:
- That the query is exhibiting unexpected results.
- Encounter an error message saying “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.”
- Or the query can prompt for the value of old field names.
2. The properties of the column that you have set for every column in your query may get deleted as soon as you run ‘Data Access Object (DAO)’ code.
3. When you run ActiveX Extensibility Object (ADOX) code, which is referring to a table while the Name AutoCorrect feature is enabled, then you may find that some properties of fields of various queries are missing.
4. Name AutoCorrect is not able to fix the changes made in the fields of a Union query.
Issues with ‘forms’
1. The Name AutoCorrect Feature at times becomes unable to update the changed field name, table name, or query name of a form and displays various unexpected results.
2. Many times when you open a form after renaming fields of a table, then you become unable to enter values of the parameters.
Issues with ‘reports’
1. This feature of MS Access 2000 at times becomes unable to repair reports as when you open a report after changing a query name, table name, or field name, then you may prompt for old field name.
2. You may find that your printer settings are lost when you enable Name AutoCorrect feature in MS Access 2000.
- It does not work with ‘macros’ and ‘code’.
- Exhibits serious performance issues.
In almost all above mentioned situations, the data on your Access 2000 database becomes inaccessible as Access 2000 gets corrupt. To repair corrupt MS Access database, it is recommended to use an effective Access database repair software. These tools are best ways to fix the issue with your Access database and recover your data.