[Date Prev][Date Next][Thread Prev][Thread Next]
[Author Index] [Date Index] [Thread Index]
[SQR-USERS Info] [SQRUG Home Page]

Code 14 from linked SQR; GPF when first row fetched



Hello all,

Actually, this is a two-part question.

We've linked a front end onto SQR 3.0.10 (16-bit for Windows) and it's been running fine for years. We pass a command line and run one of about 80 SQR reports.

Suddenly, one of my customers reports that, when she runs a particular report, the module GPFs and hangs ber computer (Windows 95, 24Mb).  Actually, Windows reports that my module has caused a GPF in ORA7WIN.DLL at 0002:000002C2. Further investigation with debugging statements shows that it's happening when the first row is fetched in a particular query; also, it has something to do with either the size of the cursor (we're fetching 26 rows of various types) and/or the presence of an nvl function in the list (it operates correctly without any of the nvl() functions, but blows up as soon as any one of them is introduced).

This _is_ one of the largest queries in the system, but it has been working fine for years, and if fact works fine at all the other clients' sites.  This is hard to work on via pcAnywhere, as it blows up the system when it fails, and I have to get them to restart, etc.

Part I:  Any ideas on the cause of this blowup problem, or how to debug it further?  The host DB is Oracle 7.3.  The Oracle DLLs at their site are the same versions I have. SQRDIR is pointing to the correct directory.  And remember, this only blows up at one site on one query.

part II:  We also supply the driver module linked to the dynamic SQR libraries, the ones that execute SQR via the SQRWIN.DLL module.  The clients don't use this version, but I do here (on Windows NT).  When I try to run this at the client site, I get return code 14 from the sqr() function.  In version 4, this means "Problem with SQRWIN.DLL", according to Chapter 22 of the user's guide.  Does it mean the same in SQR version 3?  I know it's finding the DLL ... if I rename it I get a WinExec error.  I don't think it's memory, as there's plenty of swapfile available. Anyone have any ideas on what code 14 might mean?

Thanks.

Dave



Dave Donnelly           <dave@isisbio.com>  or  <isisdave@usa.net>
ISIS BioComp            phone (909) 677-2446      fax (909) 677-3991