printing object dependencies
Thank you for taking the time to report an issue.
What's wrong... Please write below.
I'd like to be able to search all non-table objects in a given MDB for a given text string. Is this possible? I want to know which MS Access objects contain the specified string. (I haven't seen anything in the menus that looks promising.)
My intention is to identify dependencies: if I want to delete, say, a query, I want to be sure that nothing references it. Yes, I know that there's an Object Dependencies option, but there are some Unsupported Objects that Object Dependencies cannot work with. I have union queries and subqueries that would be a problem for Object Dependencies.
I have the proper permission, the objects are not open etc. I have tried clearing the Track name AutoCorrect and starting over. I have watched it map tables, queries, forms and reports but I get the "cannot enable Name AutoCorrect" message as soon as it gets to the Macros and Modules.
I know those things aren't supported for viewing dependencies, but why can't I getthe dependencies for the other objects that it appears to have mapped?
The code in my forms events use a lot of query definitions which depend on queries.
Is there a way to see which functions depend on which query, that would make things easier in code maintenance
I was reviewing and analyzing all the tables and decided to find out the Object Dependencies for each one.
Much to my surprise I discovered that Table A shows that the objects that depend on it are a bunch of queries, and Table B!
When I click on object dependencies for Table B I find out that the converse is true!
I have checked the primary key/foreign key for each table and these are fine, and have no effect here.
Neither table uses Lok-up as the data type!
Is there a utility, add-in or homebrew way to output the object dependency information from Access 2007? I know there are a couple retail solutions out there.
I went to 'Database Tools', 'Object Dependencies' and started selecting each object to verify what they depended on and what depended on them.
I came across this one and for the life of me I cant figure out what dependency is missing. Every thing works fine but I would still like to know what I did during the build process that caused this to happen and how I can fix it.
A part of me says don't worry about every thing works. The other part that wants to learn something says figure it out and don't leave well enough alone.
With that in mind, the learning part of me is asking for
How do I delete a dependency that is hidden somewhere? Is there anything that will show me where Access thinks a dependency exists?