Re: Stack Fault in Win3.1 application when accessing an oracle db

Muhammad,
If you application is written in LabVIEW, I don't know how much control you have over the stack size, but you should try to increase it.

I have written a lot of programs using C and that ODBC driver, and have needed a stack size of at least 30K. The amount of memory in your machine isn't really a factor. It's a Windows thing related to segments and stuff. Some databases need more, some need less. I called Intersolve about it once, back when they still took phone calls, and asked them about the stack size problem, and they said they recommended 80K, if you can believe that.

If the LabView language won't let you increase the stack size, you can try calling LabView (National Instruments?) and ask them how big they made the stack when they compiled their application.
Hope that gives you an idea.
Steve

Muhammad Zafar wrote:
>
> I am getting a number of errors when a win3.1 appln (LabVIEW) tries to
> connect to an Oracle 7.1 database server, including:
> Stack Fault in module LabVIEW.exe
> GPF in module LabVIEW.exe
>
> The application uses the Intersolve Oracle ODBC driver (qeor707.dll)
> v 2.11 9/8/95 . I am using SQL*Net2.1.4.1.4D, Oracle TCP/IP Adapter
> 2.1.4.1.3C. I am able to access the db thru SQL*Plus. After enabling
> tracing of SQL*Net I figured out that the application *IS* able to
> successfully connect to the database, but when the control passes back
> to the application (SQL*Net -> ODBC -> appln) it causes it to crash.
>
> I have tried unloading unnecessary drivers but to no avail. In addition
> I checked for multiple copies of the odbc driver but did'nt find any.
> Could someone shed any light to this problem? I forgot to mention that
> the computer has 16MB of RAM.
>
> Thanks
>
> Muhammad
Received on Thu Jun 06 1996 - 00:00:00 CEST