Error message re MSOWC.ddl

[Guest]

I've written a dB in Access 2000 but when I run it on an Access 2003 /
windows XP Professional platform I get an error message which says "Your
Microsoft Office Access database or project contains a missing or broken
reference to the file MSOWC.ddl version 1.0." There is some advice on what
to do (Examine the Available references in the References dialogue box in
the VB editor) Done it - no mention of MSOWC.ddl. Any ideas where to
download this ddl file and where to file it so the dB will run properly? It
seems to run OK until I print reports and then soome fields come out with
"#Name?". There may be other probs I haven't spotted as the dB isn't
perfect yet.
--
Many Thanks for trying to help.

best wishes

SupernovaKarl

 

[Tony Toews [MVP]]

I've written a dB in Access 2000 but when I run it on an Access 2003 /
windows XP Professional platform I get an error message which says "Your
Microsoft Office Access database or project contains a missing or broken
reference to the file MSOWC.ddl version 1.0." There is some advice on what
to do (Examine the Available references in the References dialogue box in
the VB editor) Done it - no mention of MSOWC.ddl. Any ideas where to
download this ddl file and where to file it so the dB will run properly?

Somehow that reference got added to the MDB on your own system. But
you almost certainly don't need it. So you need to remove it from
your system and then all should work well.

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, delete
from the references list and Compile and Save All. Keep any
necessary references and ensure they are distributed to the target
system.

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/

 

[Guest]

Many thanks for your helpful advice. I have the first 4 references you
listed plus Microsoft Office Web Components but no reference to WSOWC.dll.
When trying to compile, I found an error releting to an undefined label.
This was in a Private Sub which, in an early version of the MDB, was used to
call an ActiveX object (Excel spreadsheet) which I hoped to use on a form but
then deleted. I suspect the MSOWC.dll error is somehow related to that. I
deleted the Private sub entirely and the MDB then complied OK. I wont know
if the error message disappears until I try to run it on the other computer
with Access 2003. Previously, I also has a Data Entry page in the database
which is also now disgarded. This might be the reason for the Microsoft
Office Web Components reference do you think?

 

[Tony Toews [MVP]]

Many thanks for your helpful advice. I have the first 4 references you
listed plus Microsoft Office Web Components but no reference to WSOWC.dll.

"Microsoft Office Web Components" is the reference to remove. Look at
the initials.

When trying to compile, I found an error releting to an undefined label.
This was in a Private Sub which, in an early version of the MDB, was used to
call an ActiveX object (Excel spreadsheet) which I hoped to use on a form but
then deleted. I suspect the MSOWC.dll error is somehow related to that. I
deleted the Private sub entirely and the MDB then complied OK. I wont know
if the error message disappears until I try to run it on the other computer
with Access 2003. Previously, I also has a Data Entry page in the database
which is also now disgarded. This might be the reason for the Microsoft
Office Web Components reference do you think?

Yes, adding an ActiveX object to a form or report will add a reference
in your code as well. So that explains how it got there in the first
place.

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/