Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / .NET Framework / Interop / August 2006

Tip: Looking for answers? Try searching our database.

VB2005 Referance Problem

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Steve954 - 24 Aug 2006 20:46 GMT
The project I am developing uses a third party COM component which references
both the Microsoft ActiveX Data Objects 2.7 Library and the Visual Basic for
Applications COM objects. When I add the third party component to my project
the other two get added automatically as expected. Up until recently
everything was working fine, however now I get a series of error messages,
see below, preventing the project from being built.

Reference required to assembly 'ADODB, Version=7.0.3300.0, Culture=neutral,
PublicKeyToken=b03f5f7f11d50a3a' containing the type 'ADODB.CommandTypeEnum'.
Add one to your project.

I have tried uninstalling the third party component and reinstalling it as
well as removing the references and re-adding them but am unable to resolve
the problem.

I am fairly new to dot.net so this is causing me some major concern, any
help or advice would be greatly appreciated.

Many Thanks
Steve954 - 24 Aug 2006 21:23 GMT
I need to add a bit more to this for it to make sense.

If I add a reference to the adodb.dll 7.0.3300.0 installed in C:\Program
Files\Microsoft.NET\Primary Interop Assemblies it does not set correctly
reporting that it cannot find the path. If I uninstall 2.7 it reports errors
sayng that it requires it. Basically my project requires both these adodb.dll
versions but they seem to be conflicting however they were working fine
together but I am not sure what has changed to now cause the problems.

Many Thanks

> The project I am developing uses a third party COM component which references
> both the Microsoft ActiveX Data Objects 2.7 Library and the Visual Basic for
[quoted text clipped - 15 lines]
>
> Many Thanks

Rate this thread:







Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.