Cannot Use Object Dependencies Function in Access 2013

Question

I have an Access 2013 database with literally hundreds of objects in it that I have been building for over 15 years.  As our business processes have changed, some of these objects are no longer used.  I'd like to streamline the database by creating a new database and importing into it only the objects we're actually using.  However, I first need to figure out which of these objects (particularly the queries) are critical sub-queries and which ones are deadwood that I don't need to carry over.  I tried to use the Object Dependencies function, but I keep getting this error:

Is there any way to determine which objects are causing the problem?  The database is an Access 2013 front end with a SQL Server backend, and I am the owner of all the Access objects.  Failing that, is there any other way to get to the dependency information?

Answer 1

I would create new blank 2013 database, and then attempt to import all the objects. I suspect that a form or some object is damaged/corrupted. You quickly find out by importing all objects into a new database – if the import into the fresh database works, then you likely will be able to use the dependency checker.

And yes, the dependency checker is a fantastic built-in tool that few realize exists.

Regards,

Albert D. Kallal (Access MVP)

Edmonton, Alberta Canada

Answer 2

I first started creating this database in Access 97, and I have created nearly every object in it.  The error message indicated that it might be a permission issue, but I don't think it is.

Answer 3

FWIW, the best tool I've found to do this is the Total Access Analyzer from FMS inc. Luke Chung and his crew have done a remarkable job with this, and it will give you the most detail possible for doing things of this nature. It's not cheap, but it can save you hours/days of work with that many objects.

Total Access Analyzer: http://www.fmsinc.com/MicrosoftAccess/BestPractices.html

Answer 4

> I have an Access 2013 database

>  I am the owner of all the Access objects

These two statements do not jive. The second one suggests Access Workgroup Security, which is not available in an A2013 database (assuming native ACCDB). Can you explain?