I am trying to do thins on a win2000 PC
this what the SQL.INI looks like
[win32client.dll]
comdll=sqlora32
;comdll=sqlodb32
[ODBCrtr]
ferslong=off
remotedbname=ACT,DSN=ACT
[oragtwy]
remotedbname=ACT, @ACT
longbuffer=32760
maperror=OFF
[win32client.ora]
log=c:\temp\oracle.log /Tx /Ld
first thing is that you have the same ODBC DSN as the alias
of the Oracle database. Gupta has an undocumented feature
that it tries to connect through ODBC first even though
it is not a valid comdll (this works different in SQLTalk
and SQLWindows btw). So either rename your Oracle alias e.g.:
[oragtwy]
remotedbname=ACTxxx, @ACT
or delete the sqlodb32.dll or rename your DSN in the ODBC
Administrator.
Second, delete the file ociw32.dll from your Gupta directory,
and your Windows SYSTEM directory... The only ociw32.dll that
should stay is the one directly from Oracle in the Oracle\bin
directory.
Third, check the registry [HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE].
Are the values of ORACLE_HOME, ORACLE_HOME_NAME and
ORACLE_GROUP_NAME correct?
Which version of Oracle and Centura/Gupta do you use exactly?
HTH,
Lubos.
sco...@idx.com.au (Stuart Cowen) wrote in message news:<c2b4ed1.03033...@posting.google.com>...
the version of oracle is 7.3.4, 8.1.7 and 9.2.1
the Gupta ver is 2.0.0 ptf 2
is the ODBC connectivity better then the native dll or vis versa?
lv...@miesto.sk (Lubos Vnuk) wrote in message news:<b963529b.03040...@posting.google.com>...
I have never tried ODBC with Oracle but I think it is a bit slower.
My recommendation:
1. SQLODB32.DLL
2. OLEDB
3. ODBC
Read a paper from Gupta:
http://www.guptaworldwide.com/tech/whitepapers/SQLBase%20Open%20Connectivity.pdf
Lubos.
sco...@idx.com.au (Stuart Cowen) wrote in message news:<c2b4ed1.03040...@posting.google.com>...