Object Dependency repeatly prompts for OK to search

[jjlogan]

Object Dependency feature used to do automatic refresh when I select a different object to check on. Now, it prompts me each time for OK response and then goes through search routine showing progress bars. My Access 2007 has Options / AutoCorrect Tracking set up. I am working in split database's front end; the tables are linked and reside on network drive. Thanks for any input. Jeff

 

[kjv1611]

There's not enough information here to tell us what is really going on and what you're really trying to do.

I will say one thing for starters: If this is an Access 2007 or 2010 database (.accdb) then You NEED to turn off Name AutoCorrect... uncheck it in the options. That is very well known to cause corruption.

Here's a good reference on it:

http://allenbrowne.com/bug-03.html

So make sure that is unchecked in any database you build, ever, if it's an .accdb file. That is unless they correct the issue in future versions of Access.

Otherwise, give us some more detail, and maybe you can find a solution.

"But thanks be to God, which giveth us the victory through our Lord Jesus Christ." 1 Corinthians 15:57

 

[jjlogan]

Problem Solved.
Thanks for the feedback KJV. I referred to your Allen Browne reference, and it only referenced Access 2000 through 2003; I am using Access 2007. But it was still informative. Those references state the problems with Name AutoCorrect.
I do need Name AutoCorrect turned on because I act as database creator and DB Administrator; as such I need to often use Database Tools / Object Dependencies to see if I need to maintain an older table or query or report.
I just tried the Database Tools / Object Dependencies on some tables and on some queries, and for some reason it works now the way it it suppose to; i.e. Obj Depend refreshes automatically for each new object I am asking about; it no longer informs me by Dialog form that it must initialize all dependencies and "this could take some time to complete." I don't know why it is again working the way it used to. My test was in a database that is not being shared; it's just on a folder in the department network that only I use. Maybe I will have problems when using Object Dependencies in a database that has mutliple users in the database at one time; I will try that later when others are using our shared db.

 

[kjv1611]

Hmm, so sounds like you're saying it's solved, but you don't really know if it's solved.

On the names Autocorrect feature, he does mention it for the newer versions of Access, and he DOES mention Versions 2007 and 2010. It's right here:

The workaround is to turn the feature off:

In Access [highlight]2010[/highlight], click File | Options | Current Database, and scroll down to Name AutoCorrect Options.
In Access [highlight]2007[/highlight], click the Office Button | Access Options | Current Database, and scroll down to Name AutoCorrect Options.
In Access 2000 - 2003, the Name AutoCorrect boxes are under Tools | Options | General.

You must remember to do this every time you create a database, preferably before creating any other objects.

And if you DON'T turn that off, then pray your database doesn't get corrupted. That one feature is a very big culprit in database corruption. Well, I guess you could just make sure you have VERY frequent backups of the database if it is used often... particularly in a networked multi-user environment.

Either way, once you do test further, and verify your issue is ironed out, post back, and let us know, or if you have to go back to the drawing board, let us know that as well.

"But thanks be to God, which giveth us the victory through our Lord Jesus Christ." 1 Corinthians 15:57

 

[jjlogan]

Yes, I will keep your caution in mind, and turn OFF Name Auto Correct. Then when I need to find out what objects are dependent upon what objects, I will use a copy of the production database for that analysis.
Also, I will post back if I find further enlightenment on Name Auto Correct solutions or bad experience.
Thanks, Jeff