Re: SQL*Net and Windows Memory

In article <2qbjq1$886_at_hp06.ux.syncrude.com>, cory.aston_at_syncrude.com writes:

>>Whenever we run SQL*Net from Windows 3.1 using the Chameleon winsock
>>application we encounter a problem with the use of low memory. Typical
>>applications such as Excel and Word use less than 30k of low memory to run
>>while applications which connect to Oracle through SQL*Net use anywhere from
>>180k to 250k. This causes an error "Not enough Memory to start this
>>application" whenever another application attempts to start afterwards. This
 

>>occurs with both PowerBuilder and Visual Basic applications using both
>>proprietary and ODBC connects but only when we are connecting to Oracle.
 

>>Has anyone else experienced this problem. Have any resolutions been arrived
 at
>>to solve it.
 

>>We are running Version 1.117 of SQL*Net and Version 3.11N of Chameleon
 

>>Thank you for your responses;
 

>>Cory Aston
>>Information Technology
>>Syncrude Canada Ltd.

I am running with SQL*Net 1.2, Windows 3.1, Version 4.0 of Chameleon and have had no problems. I run with Powerbuilder 3.0a, PC-XWare, Wordperfect 5.2, Packrat 4.1 simultaneously and have had no problems. The only time I have ever encountered a problem is when I run MS Access 1.1. This usually results in a lot of resources being used, but I don't think I have a memory problem. You might want to take a look and the low memory management in DOS and the configuration of your device drivers.

Rick (rcronau_at_aol.com) Received on Thu May 12 1994 - 04:10:02 CEST