Connect OS/2 via ODBC to MS SQL Server 6.5

Connect OS/2 via ODBC to MS SQL Server 6.5

Post by Stefan Wani » Thu, 20 Mar 1997 04:00:00

We are trying to establish an ODBC connection from the WIN/OS2-emulation to
a MS SQL-Server 6.5 on an NT 4.0 server (running NETBIOS and TCP/IP).

By trying the standard NAMED PIPE protocol we get no connection to the
server neither with ODBC nor with ISQL (16 Bit tools in WIN/OS2). By using
the TCP/IP protocol we get a connection, but we get many ressource problems
in Access 2.0 when we establish an ODBC connection to the SQL-Server.

We also tested the named pipes connection with the enclosed programms
"makepipe" and "readpipe". The OS/2 station can establish a connection but
the data is not received correctly on the server. Very different characters
are displayed on the server (sent: hello, received: something like "0 ").

I don't think that there is something wrong with the server, cause from an
WIN95 client everything works perfectly with named pipes.

So, is there anybody out there, who can establish a connection from an OS/2
workstation with ODBC or ISQL to MS SQL-Server 6.5 on a NT-Server using
NAMED PIPES protocol? Help is needed, cause I definitly see no way to
establish the connection.

Thanks very much in advance.

Stefan Wania
Securitas Versicherungen


1. Connecting to MS SQL Server 6.5 via MS Access 97 and ODBC


to describe the environment briefly, we have MS Access 97 (Service Release 2)
which accesses the MS SQL Server 6.5 (Service Pack 5). Both, Server and Client
are installed on a Windows NT Workstation 4.0 (Service Pack 6). The computer is a
Pentium II 450Mhz CPU with 96Mb RAM.

The SQL ODBC driver was tested in an old as well as the current version.

Any assignments by program code (VBA) which expect an answer of the SQL server,
such as a .OpenRecordset or similar fail.
It seems as if the SQL server wouldn't follow with sending the data.
If one passes through these calls in the debugger mode, then these usually work
straight off. One experiences the same effect, if one after a call is failed in
the code, passes through it directly in the debugger mode once more.

If one changes the environment so that one evacuates the SQL server on a Windows
NT Server, then the same application works without Problems.

Can you help me?

Thanks in advance,

Sven Worm

2. Progress access via ODBC

3. Connect OS/2 via ODBC to SQL-Server 6.5

4. TempDB on a JBOD disk

5. Connecting to SQL Server 6.5 with MS Access 97 via ODBC

6. Systems Engineer/PC Developer

7. How to connect to MS SQL Server 6.5 via VB 5.0

8. Heterogeneous datab

9. Problems connecting to SQL Server 6.5 SP4 via ODBC 3.50.0305 Driver

10. Merge Replication btw MS-SQL2000 and MS-SQL 6.5 (via ODBC)

11. Can OS/2 Access SQL 6.5 (NT4.0) Via ODBC

12. Can't connect to a MS SQL-Server via ODBC

13. Connecting to SQL Server 7 from SQL S 6.5 via TCP/IP