Problems with Visual Basic/SQLNET on NT 3.5

I'm developing a VB application that accesses an Oracle 7 DB using Oracle Glue and SQLNET for TCP/IP. Everything works fine on a Windows 3.1 system but I see some strange/sparodic behaviour when the application runs on a Windows NT 3.5 system.

The only repeatable scenario is that a GPF will occur when I try to connect to a database if the database is down for some reason (like SQLNET on the server is not running). The GPF usually occurs in VBRUN300.DLL but also occurs in a .VBX sometimes. I can make the error occur every time if I add the wrong tcp/ip port to the connect string. My code makes an oracle glue Execsql() call with the connect string and the GPF occurs before the call returns.

Although the above scenario is repeatable, other sparodic behaviour also occurs. The most common scenario is that the application will not start up do to an "Insufficient Memory . . ." condition. The occurance of this failure seems to be totally unrelated to how many apps are running on the system at any given time.

Right now I'm inclined to suspect a compatibility problem with NT running VB/SQLNET apps. This is because I had even worse problems with NT 3.1 - I would get the GPF on any connect string.

I'd appreciate any info anyone might have on this problem.

Thanks,
David Dunn Received on Mon Mar 06 1995 - 15:45:03 CET