Missing or broken reference error in Access 2003 DB

[Guest]

I cant launch a particular .mdb from a server on my pc. I can launch it from
any other computer but not this one in particular. WHen opening the DB I
recieve the following error:

Your Microsoft Office Access database or project contains a missing or
broken reference to the file'sapctrl32.dll' version 1.0
*To ensure that your database or project works properly, you must fix this
reference.

Any thoughts on how I can fix the reference problem would be appreciated.
Thanks in advance for your effort.

 

[Katrina]

You have to install the specified .dll file on the computer that you are
trying to open the db on. You can see where this file should be located by
looking at the references in a module.

HTH
Kat

 

[John W. Vinson]

I cant launch a particular .mdb from a server on my pc. I can launch it from
any other computer but not this one in particular. WHen opening the DB I
recieve the following error:

Your Microsoft Office Access database or project contains a missing or
broken reference to the file'sapctrl32.dll' version 1.0
*To ensure that your database or project works properly, you must fix this
reference.

Any thoughts on how I can fix the reference problem would be appreciated.
Thanks in advance for your effort.

Two possible solutions:

1. Back up your database just in case. Open the database; type Ctrl-G to open
the VBA editor; on the menu select Tools... References. There should be a line
(with a big MISSING on it) for sapctrl32.dll. Uncheck this line's checkbox.
Click OK and then select Debug... Compile <your databasename>. If you don't
get any compile errors then - presumably - the reference was left over from
some code that is no longer needed, and you're good to go.

2. If that doesn't work - if you get a compile error highlighting some line of
code - you can then identify which Form or Report is using this reference.
Decide if you need the capability offered by the DLL; if you do need it, then
you'll need to install the sapctrl32.dll file on the new computer and make
sure it's correctly registered. You may also need to change the reference to
point to the correct folder for the .dll.

John W. Vinson [MVP]