#import MSADO15.DLL or MSADOXX.tlb
From: A Taylor (ajtaylor_at_hushmail.com)
Date: 02/01/05
- Next message: tawright915: "Re: Binding DB fields to variables"
- Previous message: Craig Kelly: "Re: MS Access automation from a C++ application"
- Next in thread: XMarshall: "RE: #import MSADO15.DLL or MSADOXX.tlb"
- Reply: XMarshall: "RE: #import MSADO15.DLL or MSADOXX.tlb"
- Messages sorted by: [ date ] [ thread ]
Date: 1 Feb 2005 08:06:06 -0800
Hello,
I am using ADO in VC++ and have a question on the issue of the #import
call. My application will be run on 98/2000/Me/NT and XP PCs and I am
developing on XP running the latest version of the MDAC <MDAC 2.8 sp1
on windows XP sp2>
I have previously simply used MSADO15.DLL in the #import call but ran
into issues with testing my application on Windows 2000. I was getting
an 0x800A0E7A error when trying to Open the connection - so I
installed the latest MDAC on that PC and all was fine.
On trawling through a few sites and on MSDN I came to the conclusion
that I perhaps should #import one of the many MSADOXX.tlb files but
the question is which one?
What is the "standard practice" for this? Do I #import an old tlb file
or is there an elegant way to check the version of MDAC installed and
warn the users that they need to install a later one <that I can put
on the installation cd>
Many thanks for your time and any help you can give me and I apologise
if this is a basic question.
A
- Next message: tawright915: "Re: Binding DB fields to variables"
- Previous message: Craig Kelly: "Re: MS Access automation from a C++ application"
- Next in thread: XMarshall: "RE: #import MSADO15.DLL or MSADOXX.tlb"
- Reply: XMarshall: "RE: #import MSADO15.DLL or MSADOXX.tlb"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
