The Sybase OpenClient library will negotiate a TDS protocol version of
4.2 when logging into Microsoft 6.0 SQL Server (4.2 was that last
"common" Sybase/MicroSoft protocol). The big down side in this is the
new DECIMAL/NUMERIC datatypes will be converted to float when sending
data back and forth, possibly losing precision. In addition, any System
10 features (e.g. client side cursors) in OpenClient will not be usable
against the server. Otherwise, I haven't seen any problems.
I don't know enough about the web.sql product to comment on it.
Otto Lind Otto Lind Consulting Services
skypoint!olcs!otto voice:(612)457-1080 fax:(612)457-0761
To add just a little bit to what Otto said: web.sql uses CTlib to access
the SQL server. I don't think that aceessing a SLQ server 6.0 instead of a
Sybase server will be a problem (The underlying software is certainly able
to do it...)
Can someone give me some suggestions on how to have a program on a Silicon
Graphics system write database records to a Win2K/SQL Server2K system. I
have experience using ODBC to transfer data from a WinNT/Win2K system, and
theoretically ODBC should work for this purpose. I just haven't found much
information about what companies have ODBC drivers for this connection.
2. MS-SQL response and total users ( I need info defense)
3. Sapphire/Web, Netscape, SQL Server, IRIX - JDBC Driver?
4. USA-NJ-ORACLE DATABASE DEVELOPER WITH JAVA STORED PROCEDURES
5. (no subject)
6. Microsoft SQL Server 7 and Microsoft SQL Server 2000 Driver for JDBC
8. Microsoft Sql Server Training : Hands-On, Self-Paced Training for Microsoft Sql Server Version 6.5
9. Microsoft SQL Server 7 with Microsoft SQL Server 2000 Driver for JDBC
10. Microsoft Sql Server Training : Hands-On, Self-Paced Training for Microsoft Sql Server Version 6.5