Re: MDAC 2.7 with Win XP SP2

This is not an MDAC issue or a COM issue, it's a compiler issue. So I don't
know the answer.

Paul

"Shads" <Shads@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:1678D30D-6496-4BC5-A310-70CD2B25E1E0@xxxxxxxxxxxxxxxx
It's more of a temporary solution until everyone upgrades to SP2. It did
resolve the references but when I recompiled the solution I received
errors
"[Project] makes an indirect reference to assembly ADODB" and then it
complained about the ADODB.Recordset method. Any Ideas?

"Paul Baker" wrote:

That doesn't sound like the right solution. Is this a registry entry that
must be made on all clients? It can be done without any registry entries
at
all.

Paul

"Shads" <Shads@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B472575C-7D7A-4ED8-92E9-9B2A5A77B4D6@xxxxxxxxxxxxxxxx
Thanks for your help Paul. We got it working by adding the
PrimaryInteroptAssemblyName Reg Key for the 2.7 ADO object

"Paul Baker" wrote:

This is more of a COM question, I think.

If your software is version neutral, just use the version neutral
ProgID
or
ClassID for the objects you wish to create.

Paul

"Shads" <dsharrad@xxxxxxxxxxxx> wrote in message
news:1140604215.684751.319400@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I have two computers one has MDAC 2.7 on Win XP SP1 the other
computer
has MDAC 2.8 SP1 on Win XP SP2. I have a project written in VB.NET
which references ADODB.dll version 2.7 (just for your information
this
code was written in VB6 using ADO and has been converted to VB.NET,
we
haven't changed the code to use ADO.NET due to project timescales).
When I open the same project on my Win XP SP2 machine, I receive a
missing reference.

How do I go about resolving this problem?

I don't really want to upgrade my Win XP SP1 machine to use MDAC
2.8.
I believe this will then affect my Windows 2000 Server where the
code
will eventually be deployed?

Thanks









.

Relevant Pages

  • Re: Alternate file types for RUN ?
    ... resolved at link time and are fixed. ... The references to the RTL routine symbols/entry points are only partially ... as a shareable image name and an offset. ... doesn't need to resolve this). ...
    (comp.os.vms)
  • Re: Suddenly VB6 database program quit working - HELP!!!
    ... References are OK. ... I tried another project that had been working and it fails the same way. ... I haven't installed anything for awhile except MDAC 2.8 and possibly ... >¤ It fails on the Set statement. ...
    (microsoft.public.vb.database)
  • Re: MDAC 2.8 Update Problem
    ... If you upgraded to MDAC 2.8 and Component Checker shows that installation is ... They start with 2.80 and Component Checker find the Version ... I want to upgrade this references to 2.7 ...
    (microsoft.public.data.ado)
  • Re: Code to Color ActiveRow Columns A Through C
    ... Most people have problems with offset/resize ... ... (Win XP Pro SP-1 XL2000-2003) ... > 2) Having to resolve the range reference. ... Resize is very fast compared> to resolving a string references. ...
    (microsoft.public.excel)
  • Re: "cant find project or library" error has started appearing in VBA running on Word 2003
    ... In the VBA editor, ... Most likely one or more of the references are marked as 'MISSING:' and need to be resolved. ... into the immediate window all is OK ... but this does not resolve the issue ...
    (microsoft.public.word.vba.general)
Quantcast