Problems with Q&E Driver with VBasic and Informix

Problems with Q&E Driver with VBasic and Informix

Post by Visual Basi » Fri, 07 Oct 1994 18:53:26

I have some problems with the ldllsqlw.dll library provided by Q&E Software
and I-NET PC to manage INFORMIX databases through ODBC.

The layers I use are:

DOS 6.0
I-NET 4.10
Q&E driver for Informix
VB PRO 3.0

Q&E recommends the ldllsqlw.dll library must be in conventional memory,
so it provides a utility to use at windows startup to force this.

These are some of the problems I have:

- Once I have got a connection error, the I-net layer returns an error
  (Unknown error -854) and remains busy, so the only thing I can do is
  reboot the computer. This problem is a known-error for Informix.

- If I make an .exe file for a vb application, I can execute the application
  only once. The second time I got a GPF, sometimes in VBRUN300.DLL,
  sometimes in LDLLSQLW.DLL. I could solve this problem unloading the dll,
  but the I-net layer remains "busy", so ALT-CTRL-DEL is again the only

- Sometimes, "An error in your application ..." message from vb or a GPF
  appears "ramdomly"; always when an ODBC call is made.

These are some of my questions:

- Is there another 3th party dll's for accessing Informix via ODBC?
- Have Informix already released I-Net 5.10?
- Q&E Technical Support FAX/PHONE or E-mail address?
- Any bibliography you can suggest to understand what's happening?
- Any utility to trace the vb application and odbc calls?

Any suggestion would be of great help.
Thanks in advance


1. Enabling TCP/IP server protocol BUG in SQL2K and SQL Server 6.5 native driver Qs

(1) SQL Server 6.5 native driver: Ntwdblib.dll. I know this dll has prob not
been updated since v 6.5, but, can this net lib use 'shared memory' as a
means for client server communication?

(2) Is there a white paper out there that talks about how sql server clients
would connect to the server with all the various protocols? What if the
client and server have more than one communication protocol enabled.. which
one wins out? Is there a paper on the guts of how this communication takes

(3) Im seeing a genuine SQL Server Bug that I can recreate on mux machines.
If I disable all my protocols from my Server Network Utility in SQL Server
2000... it defaults to shared memory. Now if I add back TCP as the enabled
protocol.. it DOES NOT get enabled. I can see from my event viewer that only
"shared memory" has been enabled and not TCP, even though Ive selected it in
my server utility. This was tested on a Win 2k server and professional
machine and I could break it both times. Never did get back TCP as a server
communication protocol.


2. Which SDK to access Sybase???

3. Visual Basic - ODBC - Informix OnLine Qs.?

4. How to store image ?

5. 2 Qs: Column statistics & selectivity

6. cursors Vs for loops in pl/pgsql

7. JDBC driver with "Locale = es"

8. foreign characters - newbie question

9. 3 Qs about tracing & tkprof

10. JDBC Driver with es Locale.

11. 13707-OR-Greater Eugene Area-Software Development-SYBASE-ORACLE-Ingres-Informix-