Broken reference

Topic

New Reply

I am coding a procedure in Access97 to check for broken references, e.g. to my own codelibrary. This procedure is located in a separate module and is called first of everything via Autostart-macro. It should also try to repair the link by searching for the library at some other folder.
But if the link to that library is broken indeed, Access does not execute the procedure at all. Instead it halts and highlights commands like Left(strXYZ,intN) or Right() or Space$(), telling “The library was not found”, although the code in this module does not call any of the functions or globals in my library.

Reply | Quote

Replies

Yes, I’ve run into the same problem with my own libraries of procedures. Any broken reference will cause this kind of behavior, no matter which reference it is.

What you might try is checking the reference to the Microsoft Visual Basic for Applictions Extensibility Library, which is what is used in a lot of wizards and add-ins to provide access to the built-in utility functions without having an object model specified (i.e., DAO or ADO) in the add-in’s references.

Compile the code and see if it balks at anything with the broken reference and the extensibility library in place. If it does, try adding a specific VBA.Left, etc., instead of just Left, and see if that allows it to compile.

Reply | Quote

> try adding a specific VBA.Left, etc., instead of just Left.

YEP! That was the solution. Now my code runs and can search for the missing referenced library.
BTTF*

* Bowing To The Floor

Reply | Quote

Your adoration is appreciated. Thanks!

Reply | Quote