Re: SQLRUN50 error when calling a stored prcedure.

Maybe this is also a problem due to conflicting DLL's (see current thread about "Oracle73 and SQLTalk Problem" in this newsgroup).

When you login to Oracle before you start your SqlWin app, SQLPlus loads all neccessary DLL's it needs to connect to Oracle. These DLL's are
corewin.dll, ora7win.dl, ora73win.dll, usdmem.dll and some more.

If you start your SqlWin app, SQLAPIW.DLL loads SQLORAW.DLL (Centura's Oracle router) which is based on the DLL's I mentioned before.
Because these DLL's are already in memory, SqlWin "reuses" them.

If SqlPlus ist *not* started, these DLL's are not in Windows memory. So
SQLAPIW/SQLORAW will force Windows to load these DLL's. Windows itsself checks your windows and windows/system directory and the PATH to find these DLL's. And I guess your PATH containes first a reference
to your SqlWin directory and after that to your oracle\bin directory.

If you move the conflicting SqlWin DLL's (corewin.dll, ...) out of your PATH
I bett that SqlWin has no problems running against Oracle...

-- 
Stefan
Assling/Germany
My no spam email address is stefan_misch at msn.com
Please do not reply directly to this posting.

Poon Chak Yau <cypoon_at_hknet.com> schrieb im Beitrag
<3349fecd.62912296_at_bull.hkstar.net>...


> Hello,

> 	I am running Oracle 7.3.x on HP-UX and SQL Windows 5.0.3 on a

> Windows 3.1 computer.

> 	I gets the following problems when my application call a

> stored procedure from SQL Windows. The program reports SQLRUN50

 error


> and SQLORAW.DLL cause GPF.

> 	However, the program runs prefectly if I login Oracle with SQL

> Plus before I run the SQL Windows application.

> 

> 	Can anyone provide help to me? Any suggestion are welcome.

> 

> Regards,

> 

> Poon Chak Yau.

>