MSADODC.ocx

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

sid - 23 Feb 2007 03:41 GMT

I have an existing project that is quite extensive and I wanted to
add
one more module, but in the module I use: dim cn as new
ADODB.Connection

In the test project I added the MSADODC.ocx to the references and it
worked well.

Now, when I try to add the test project to the existing project I get
the error: "Name conflicts with existing module, project, or object
library"

How do I determine what I have a conflict with ?

Any help is appreciated.

Sid.

Reply to this Message

Ralph - 23 Feb 2007 11:15 GMT

> I have an existing project that is quite extensive and I wanted to
> add
[quoted text clipped - 13 lines]
>
> Sid.

In References check what "Microsoft ActiveX Data Objects 2.x Library" you
are using in each.

-ralph

Reply to this Message

sid - 23 Feb 2007 15:10 GMT

> > I have an existing project that is quite extensive and I wanted to
> > add
[quoted text clipped - 20 lines]
>
> - Show quoted text -

No version of "Microsoft ActiveX Data Objects ..." is installed in
either project.

Sid.

Reply to this Message

Ralph - 23 Feb 2007 19:37 GMT

> > > I have an existing project that is quite extensive and I wanted to
> > > add
[quoted text clipped - 25 lines]
>
> Sid.

Well then, its time to assume you didn't make a typo in your first post ...
<g>

When you say you "added the MSADODC.ocx to the references" - did you really
mean to the "Project->References" (where it does not belong) or to the
"Project->Components" (where it does) ??

Also how can you compile this line ...
Dim cn as New ADODB.Connection
without having a reference to some version of ADO?

-ralph

Reply to this Message

sid - 23 Feb 2007 22:15 GMT

> > > "sid" <sidwe...@alexian.net> wrote in message
>
[quoted text clipped - 45 lines]
>
> - Show quoted text -

I copied it from an example I found on line.
And it did work. I referenced it.
I know the ocx(s) don't belong in the reference list, but I have seen
examples on-line do it successfully.
So I went along. (thought it was some undocumented technique)

My solution was to edit the vbp project file with wordpad and remove
the MSADODC.ocx reference manually.
Then went in and added it to the components list. I had to paste an
instance on a form before the module would work though.

Either way, I need the objects that are contained in the MSADODC.ocx
for my code to work.
Why it worked on the first project with just a reference I don't
understand completely.
Then again why I can just place an instance of the ocx on a form and
not reference it and my code works, I don't totally understand either.

Thanks

Sid.

Reply to this Message

VB Forum / Database Access / February 2007

MSADODC.ocx