Re: VB4.0(16bits)->Jet->MDB->ODBC->SQLNet->TCP-IP question.
From: DriftWood <drift_wood_at_my-deja.com>
Date: Tue, 19 Dec 2000 21:16:24 GMT
Message-ID: <91oj71$hvv$1_at_nnrp1.deja.com>
"It is a kind of good deed to say well; and yet words are not deeds. -William Shakespeare"
Date: Tue, 19 Dec 2000 21:16:24 GMT
Message-ID: <91oj71$hvv$1_at_nnrp1.deja.com>
On Windows 9x Microsoft assumed that you would want to bridge your ODBC 16-bit applications to the latest 32-bit drivers if such were available and so they included a gneric thunk for 16-bit ODBC. You can still install and configure the 16-bit SQL*Net client and create a DSN (using the 16-bit ODBC administrator) and use that DSN from within your 16-bit application. For Oracle, this is the suggested path as there were some odd problems that could arise if you tried to use the 32-bit drivers from a 16-bit program.
The 16-bit oracle home directory is (and must remain) separate from the 32-bit oracle home.
--
-cheers
DW
"It is a kind of good deed to say well; and yet words are not deeds. -William Shakespeare"
Sent via Deja.com
http://www.deja.com/
Received on Tue Dec 19 2000 - 22:16:24 CET