Seriously, though, VB3???????????? Actually, I don't think you can. When you
use createboject against "ADODB.Connection" what happens?
"Chang Cocho" <chan...@hotmail.com> wrote in message
news:#6g5v4ofCHA.2436@tkmsftngp10...
> I need to connect a VB3 app to a SQL server 2K database
>
> My box is a WinXP pro!!
>
>
> Any Ideas????
>
>
Hmmm... VB3 was pre-ADO (and 16 bit), so it probably doesn't support
ADO. That leaves the ODBC API or DAO. Not wanting to dust off a ton of
old notes on the API, I'd say stick with DAO - if 16 bit DAO can connect
to a SQL 2k database. There is an absolute ton of old information on VB
and DAO on the net - try sites like www.codehound.com/vb, or just do a
search on Google.
Good luck!
LL
Or if you are working from source code, if it only uses
late bound dao objects, you just replace them with dao3.6
This is a pretty unlikely scenario - more likely you would
need a complete rebuild.
(david)
"Chang Cocho" <chan...@hotmail.com> wrote in message
news:#6g5v4ofCHA.2436@tkmsftngp10...
Regards,
Gary
--
gpmusto...@hotmail.com
remove your hat to reply via email, although I read the newsgroups more
frequently than I check this account.
If not, you could try setting up a 16-bit ODBC client. I don't recall if
RDO was available with VB3 (I don't think it was). If not, create an Access
database with links to the SQL Server tables ("attach" the tables in
Access/Jet 2.0 lingo), use DAO to access the Jet 2.0 database (your
intermediary), and specify SQL_PASSTHROUGH.
HTH,
Tore.
"Chang Cocho" <chan...@hotmail.com> wrote in message
news:#6g5v4ofCHA.2436@tkmsftngp10...