Problem accessing Access database from VB2005

[John Dann]

We've got a VB2005 program written some time back that we're trying to
do some maintenance on still from within VB2005 but now running on a
Vista Business PC (which I think may be relevant to the problem).

When we go to start up the project from within the VS environment
there are several build errors relating to an inability to find the
ADOX library. I can't remember without hours of reorientation and
checking back whether this was a part of MDAC or should be accessible
from System.Data.OleDB. If it was MDAC then this is something that may
have changed in a Vista environment because IIRC the traditional MDAC
calls no longer work in the same way.

Anyone recognise this problem please and can suggest a fix?

Many thanks
JGD

[Michel Posseth [MCP]]

Vista has WDAC , and WDAC has no ADOX and you can`t install MDAC ( as it
is a lower version )
see this thread
http://forums.microsoft.com/MSDN/Sho...74386&SiteID=1

the solution seems to be to use
tlbimp msadox.dll /out:ADOX28.dll

Then put this ADOX28.dll file on your development machine and add reference
to it.
however you should do this on a XP computer wich has MDAC 2.8 installed and
then copy the resulting assembly to the vista machine
( this is how i understood it )

regards
Michel Posseth [MCP]
http://www.vbdotnetcoder.com



"John Dann" <ne**@prodata.co.ukschreef in bericht
news:qn********************************@4ax.com...

We've got a VB2005 program written some time back that we're trying to
do some maintenance on still from within VB2005 but now running on a
Vista Business PC (which I think may be relevant to the problem).

When we go to start up the project from within the VS environment
there are several build errors relating to an inability to find the
ADOX library. I can't remember without hours of reorientation and
checking back whether this was a part of MDAC or should be accessible
from System.Data.OleDB. If it was MDAC then this is something that may
have changed in a Vista environment because IIRC the traditional MDAC
calls no longer work in the same way.

Anyone recognise this problem please and can suggest a fix?

Many thanks
JGD

[Michel Posseth [MCP]]

Okay here a folowup

Copy the "%Program Files%\Common Files\System\ado\msadox.dll" from working
XP machine to Vista machine

Execute "tlbimp msadox.dll /output:MSADOXASM.dll" . This will create the CLR
assembly file "MSADOXASM.dll"

Add this assembly to your project and add the "using MSADOXASM;" statement
to your code.

and the problem should be solved
HTH

Michel Posseth
http://www.vbdotnetcoder.com




"Michel Posseth [MCP]" <MS**@posseth.comschreef in bericht
news:uD**************@TK2MSFTNGP02.phx.gbl...

>
Vista has WDAC , and WDAC has no ADOX and you can`t install MDAC ( as it
is a lower version )
see this thread
http://forums.microsoft.com/MSDN/Sho...74386&SiteID=1

the solution seems to be to use
tlbimp msadox.dll /out:ADOX28.dll

Then put this ADOX28.dll file on your development machine and add
reference to it.
however you should do this on a XP computer wich has MDAC 2.8 installed
and then copy the resulting assembly to the vista machine
( this is how i understood it )

regards
Michel Posseth [MCP]
http://www.vbdotnetcoder.com



"John Dann" <ne**@prodata.co.ukschreef in bericht
news:qn********************************@4ax.com...

>We've got a VB2005 program written some time back that we're trying to
do some maintenance on still from within VB2005 but now running on a
Vista Business PC (which I think may be relevant to the problem).

When we go to start up the project from within the VS environment
there are several build errors relating to an inability to find the
ADOX library. I can't remember without hours of reorientation and
checking back whether this was a part of MDAC or should be accessible
from System.Data.OleDB. If it was MDAC then this is something that may
have changed in a Vista environment because IIRC the traditional MDAC
calls no longer work in the same way.

Anyone recognise this problem please and can suggest a fix?

Many thanks
JGD

[John Dann]

Many thanks - I'll check this out asap.

JGD