Re: 32-bit Application using ADO under 64-bit OS (Windows Server 2003)


"Kelvin" <Kelvin@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:025ACF27-9863-44AC-AC75-429FECAD9D43@xxxxxxxxxxxxxxxx
Hi,

My VS C++ 6 application uses ADO to get data from Oracle database and save
to MS Access data file. The application import msado15.dll using #import
"c:\Program Files\common files\system\ado\msado15.dll" no_namespace
rename("EOF", "ADOEOF").

Recently, the application platform was moved from Windows Server 2000 to
Window Server 2003 on VMware's virtual environment. After the move, I am
randomly having problem where expected data was not found in the created
Access data file.

I just noticed that in Server 2003, there are actually two versions of
msado15.dll, one under Program Files folder for 64-bit libs and one under
Program Files (x86) for 32 bit libs. My question is, could my problem
caused
by my import statement above pointing to wrong library? If it is, why
does
it work 99% of time? Do I need to explicitly point the import path to
Program Files (x86)?

Thanks for any suggestion.


I doubt it is the problem. You are only reading the TypeLib contained in the
dll.
However, what might be a problem is what what you didn't tell us. What ADO
(MDAC) version are you using? Or even provider?

Windows Server 2003 comes with MDAC 2.8 SP1, with Win2k you might be using
anything from ADO 2.5 to 2.8. That would be the more likely culprit.

-ralph


.