[AccessD] Broken References in Runtime AXP

For each reference that is selected, Access does the following:

Access checks to see if the referenced file name is currently loaded in 
memory.

 If not, Access verifies whether the RefLibPaths registry key exists. If 
so, Access looks for a named   value with the same name as the 
reference. If there is a match, Access loads the reference from the   
path that is pointed to by the named value.

Access next searches the following locations for the referenced file:

1 Application Folder (location of Msaccess.exe)
2 Current Folder that you see if you click Open on the File menu
3 WinDir where the operating system files are running  XP c:\windows
4 System Folder located in the WinDir  XP c:\windows\system32
5 the PATH environment list of folders directly accessible by the system.
If the file cannot be found, then a referencing error occurs.

 You may have to do a reboot in between test runs to forcibly  remove 
reference from memory
 
Charlotte Foust wrote:

>Well, I'm now officially round the bend.  I just sat here and kept
>seeing the idiot thing report that it found the broken reference in the
>right location, which is where the file *is* but not where the reference
>actually pointed.  The FullPath property of the reference returned the
>right location instead of the broken one!  Then I watched the referenced
>library pop up in the project explorer even though it wasn't there when
>I opened the project!  I'm just going off to sit in the corner and
>gibber.
>
>I'm running Windows XP and I wonder if that has anything to do with it.
>I've also seen it report a broken reference and say it fixed it in
>runtime and have the app appear to run OK but then when I opened it
>normally and held down the shift key, the reference was broken.  Usually
>if it's broken it stays broken ... But not always!  Aaarrrgggghhhh!!!
>
>Charlotte Foust
>
>  
>