Resolve Error regarding missing object dependency

[drunyan0824]

I am getting an error message that reads "The table or query name 'Maintenance_TBL' you entered in the property sheet or macro is misspelled or refers to a table or query that doesn't exist." when I try to expand the records that I have on a table titled "tblEquip". I opened the Object Dependencies window and the missing Maintenance_TBL but I renamed this table to tblMaint. Is there a way to fix this problem? I can't find a way to change Maintenance_TBL to tblMaintenance in the objects dependencies window.

[ranman256]

never rename things once youve programmed or made queries. you get errors.
to fix, rebuild every query that references it.

[drunyan0824]

I can't find any other query that references that table. Maybe I deleted it. I am assuming if I can't resolve the error, I will have problems with my database.

Nevermind, I was wrong. all of my queries depend on that table.

[drunyan0824]

That didn't work, I just re-created a query and it was still dependent on the missing Maintenance_TBL.

[drunyan0824]

Rebuilding the query didn't work. Does this mean that I need start the database over from scratch?

[Welshgasman]

Have you checked your property sheets.?
Easiest solution would be to rename it back and learn from this.

[Gicu]

Have you tried to turn off then on the Name AutoCorrect tracking? Also, if that doesn't work try to import all objects in a brand new Access file.

Cheers,

[Micron]

You might have a calculated field using the old name in an expression (e.g. IIF function, DMax, DCount, etc.). If the problem lies in the property sheet we could be talking about a form or control that references the old name - also possibly within an expression.

[drunyan0824]

Have you checked your property sheets.?
Easiest solution would be to rename it back and learn from this.

Renamed the table and it fixed the issue. So I have the option of renaming something in access but if I do, I potentially screw up my object dependency. Then if I am halfway through creating a database and realize that I gave a table or query a confusing name I am just stuck with that name unless I start creating the DB from scratch again?

[drunyan0824]

Have you tried to turn off then on the Name AutoCorrect tracking? Also, if that doesn't work try to import all objects in a brand new Access file.

Cheers,

I didn't think about trying to toggle the auto name correction. I ended up just importing the tables into a new database.

[drunyan0824]

You might have a calculated field using the old name in an expression (e.g. IIF function, DMax, DCount, etc.). If the problem lies in the property sheet we could be talking about a form or control that references the old name - also possibly within an expression.

I checked the property sheets and the calculated fields that I have and couldn't find any reference to the missing table.

[isladogs]

The Name AutoCorrect feature isn't fully trusted by many developers but it works well provided certain precautions are taken to ensure the name changes are fully propagated through.
See my article Use Name AutoCorrect Successfully (isladogs.co.uk)

[drunyan0824]

The Name AutoCorrect feature isn't fully trusted by many developers but it works well provided certain precautions are taken to ensure the name changes are fully propagated through.
See my article Use Name AutoCorrect Successfully (isladogs.co.uk)

Thank you for the link to your article. I am a couple of questions after reading the article. Would copying and pasting the data and structure of a table, then giving the table a new name run the same risks as renaming the table? Would doing a make table or an append query be a option if I wanted to change the names and field my tables?

[isladogs]

The only risks with NAC are not ensuring each name change has been fully propagated through each affected database object. My article gives code to overcome such issues

If you copy & paste a table and its data to a new table, the dependency info will be identical to the original. So in that respect, no benefit or additional risk

Not sure what your final sentence is asking but, if you start again with a new table, you may lose any NAC info already collected

[drunyan0824]

The only risks with NAC are not ensuring each name change has been fully propagated through each affected database object. My article gives code to overcome such issues

If you copy & paste a table and its data to a new table, the dependency info will be identical to the original. So in that respect, no benefit or additional risk

Not sure what your final sentence is asking but, if you start again with a new table, you may lose any NAC info already collected

Lets say I have a table in a database called tblCategory. Then as I am building my database I realize that the name tblCategory is confusing and I need to change it. Could I create a new table called tblCableCategory that has the same structure as tblCategory and then run an append query to copy all of my data from tblCategory to tblCategory and avoid a dependence error?