Missing or broken reference

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have an access database (front end) spread out on several PC's that run
either Access 2000 or 2002.

Out of 10 PC's, two computers throw an error message when the user attmempts
to open a form from the switchboard. The error is:
"Your Microsoft Access database or project contains a missing or broken
reference to the file 'OWC10.DLL' version 1.1."

Can anyone tell me what this means and how I can fix the problem?

Thank you in advance.

Antonio
 
The file OWC.DLL is not on those machines or is not registered.

Does it occur when opening any form or a particular one?

Steve
 
Hi Steve. Thank you for answering.

I didn't try out any other buttons. I stopped after I got this first message.

What does it imply if it is one specific form and not another?
And if it is any form that is opened?

Antonio
 
Just wondered if a particular control on the form was causing the problem,
such as a Pivot Table or Pivot Chart etc.

In any case, try copying the OCW.DLL to the machines and registering it with
Regsrv32.exe.

Steve
 
Antonio said:
Out of 10 PC's, two computers throw an error message when the user attmempts
to open a form from the switchboard. The error is:
"Your Microsoft Access database or project contains a missing or broken
reference to the file 'OWC10.DLL' version 1.1."
Click to expand...

That's a pretty much useless reference regarding Office Web Components
which MS puts in when you convert a database from an older version.
Or something like that. I'm pretty sure I had that when converting
from A97 to A2000.

Do you have any references besides the basic three? Are you sure you
need them? Write down the path and name of the extra ones (or put the
following code in a module and execute the code), delete from the
references list and Compile and Save All. Keep any necessary
references and ensure they are distributed to the target system.

Dim ref As Reference

For Each ref In Access.References
Debug.Print ref.Name & " " & ref.FullPath & " " & ref.Major &
"." & ref.Minor
Next ref

For a very detailed page on reference problems see
http://www.accessmvp.com/djsteele/AccessReferenceErrors.html

Ctrl+G will take you into the Debug/Immediate window. Then click on
Tools on the menu bar and References.

The Access 2000 default references are:
Visual Basic for Applications
Microsoft Access 9.0 Object Library
OLE Automation
Microsoft ActiveX Data Objects 2.1 Library
or
Microsoft DAO 3.6 Object Library

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
 
Excellent,

How would I do they copying?

Would I find the file on my PC, copy it to a jump drive and then install it
on the problem PC?

If so, could you elaborate on the Regsrv32.exe? I am not familiar on how I
would execute it to complete the registration.

Antonio
 
SteveM said:
In any case, try copying the OCW.DLL to the machines and registering it with
Regsrv32.exe.
Click to expand...

No, no, no. OCW.DLL is very likely not required.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
 
Please forgive my ignorance...

The references that I have "checked" are:
Visual Basic For Applications
Microsoft Access 9.0 Object Library
Microsoft ActiveX Data Objects 2.1 Library
OLE Automation

As for whether or not I need them, I don't know. I know little about Visual
Basic.

All the code I have running on this database is copied and pasted w/ a
little alterations to make it work the way I need it. (I dont even know how
exactly how to "execute" the code you provided. When I pasted it into a
module I got an error message saying "Compile Error: Invalid outside
procedure")

I did have a problem with Access versions when I deployed the front end.

The 2002 PC's shut down (throwing the "Access has encountered a problem and
needs to close..." error message) when attempting to open reports. When I
converted the file format from 2000 to 2002, the crashing ceased on the 2002
PC's. Now I have a 2002 front end version and a 2000 version.

Is this perhaps where the OCW10.DLL reference came from? If so, can I just
uncheck the "missing" reference and solve my problems? Or is it more complex?

Antonio
 
the owc.dll is the "Office Web Components" dll that is installed with Office 2000/2003. It mainly provides charting functionality for office apps (e.g. Access). You can find the dll in the following default directory:
(for Office 2003):
C:\Program Files\Common Files\Microsoft Shared\Web Components\11\owc11.dll

Microsoft, embarrassed by the fact that programmers could code up apps using the dll with better functioality than the current office apps (!!!), in their infinite wisdom, dropped the dll from Office 2007 and stated they will no longer support it. They are pushing Excel Services as the new solution (a terrible coding nightmare compared to owc1x.dll).

I also noticed that the b*stards coded the upgrade to Vista/Office 2007 to automatically delete the owc11.dll.


Regards,
Preston Callicott

EggHeadCafe - .NET Developer Portal of Choice
http://www.eggheadcafe.com
 
Antonio said:
The references that I have "checked" are:
Visual Basic For Applications
Microsoft Access 9.0 Object Library
Microsoft ActiveX Data Objects 2.1 Library
OLE Automation

As for whether or not I need them, I don't know. I know little about Visual
Basic.
Click to expand...

Those are the correct references for Access 2000.

But that doesn't make any sense because previously you stated the
problem was with an OWC reference.
I did have a problem with Access versions when I deployed the front end.

The 2002 PC's shut down (throwing the "Access has encountered a problem and
needs to close..." error message) when attempting to open reports. When I
converted the file format from 2000 to 2002, the crashing ceased on the 2002
PC's. Now I have a 2002 front end version and a 2000 version.

Is this perhaps where the OCW10.DLL reference came from? If so, can I just
uncheck the "missing" reference and solve my problems? Or is it more complex?
Click to expand...

Yes, uncheck the missing reference and compile the code by Debug >>
Compile.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
 
Antonio have you resolved this error, same is what i'm getting?...

Did anyone have a good answer... ? Please send me/update the response if it
was answered?

Still havn't resolved my issues of the same sort...

Bill
 
Back
Top