Great Answer found 2

[Fishwalker]

I have seen some pple asking ms acces owc10.dll problems,
any time you see any kind of that message, make sure you go to the References and tick only for the following objects.

Visual Basic For Applications
Microsoft Access 10.0 Object Library
OLE Automation
Microsoft DAO 3.6 Object Library

un tick any other onces, and you will be ok.

 

[HarleyQuinn]

Why not just uncheck and remove the broken reference (in this case I think it's 'Microsoft Office XP Web Components') rather than a blanket "all but the stock"?

un tick any other onces, and you will be ok.

You will be OK as long as your application doesn't need any references other than the standard ones.

When removing references like this it's always best to compile your code after removing each reference to make sure that your application doesn't require it (and if it does, add them back in which should also fix the broken reference problem).

Regards

HarleyQuinn
---------------------------------
Carter, hand me my thinking grenades!

You can hang outside in the sun all day tossing a ball around, or you can sit at your computer and do something that matters. - Eric Cartman

Get the most out of Tek-Tips, read FAQ222-2244: How to get the best answers before post

 

[boblarson]

Yep, I agree with HarleyQuinn on that one.

Bob Larson
Free Access Tutorials and Samples:

http://www.btabdevelopment.com