third_party_content:community:commentary:forums_nonworks:59a16ce797f5b9e1852569a40054fcd8

Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community

XOInstance crashes OpenEngine... need help. (OpenInsight Specific)

At 27 NOV 2000 10:28:17AM Steve Carlson wrote:

Can anyone Help???

I have a SP that accesses an ODBC database. Everything work's fine

when the ODBC database is up and running. But I am accessing it through the web and need to prohibit OE from crashing when a user

needs info.

I ran the SP from the system editor's Exec. line and OE

crashes from there not only when the ODBC database isn't running but also when I simply pass the wrong "PASSWORD".

hXO=XOInstance("M204", "ODBC", "USER", "PASSWORD", , XO_USETRANS$+XO_GLOBALSHARE$+XO_LOGINDIALOG$) It's pretty obvious that when the "XOInstance" above is executed and any "Error" occurs my OpenEngine crashes, yet when I pass the wrong PASSWORD using the "Connect to Data Source" form in Client/Server Workspace (I'm guessing that the same "XOInstance" is being used to connect) I get a dialog box that there was a communication error and OE does not crash. I need to know how to keep OE from crashing when "XOInstance" is not sucessful. TIA Steve C. </QUOTE> —- === At 27 NOV 2000 11:10AM Tim Marler @ Prosolve Software (UK) wrote: === <QUOTE>Steve, Post the code that you are using so we can have a look. Tim [email protected] @ Prosolve Software </QUOTE> —- === At 27 NOV 2000 11:31AM Steve Carlson wrote: === <QUOTE>The code is below…. up to the point XOInstance crashes. Function OI_ST(Request,VarHtml) Declare Function Inet_Msg, Inet_QueryParam $insert XO_Equates WRONG_TRAINEE_DOB=' Results=" TRAINEE_SSN=Inet_QueryParam(Request, 'T_TRAINEE_SSN') TRAINEE_DOB=Inet_QueryParam(Request, 'T_TRAINEE_DOB') TRAINEE_DOB_NONE=Inet_QueryParam(Request, 'T_TRAINEE_DOB') TRAINING: * Convert "-" to In TRAINEE_SSN

Convert "-" to In TRAINEE_DOB Convert "/" to In TRAINEE_DOB

Convert @LOWER_CASE to @UPPER_CASE In TRAINEE_DOB

*

SCRIPT=SELECT T_TRAINEE_SSN, T_TRAINEE_DOB, T_TRAINEE_NAME, T_CURRENT_STATUS, T_EXPIRATION_DATE, T_CERT_NO FROM ODBC.FILE.TRAINEE WHERE T_TRAINEE_SSN=:"'":TRAINEE_SSN:"'":" ORDER BY T_EXPIRATION_DATE DESC"

hXO =XOInstance("DATABASE", "ODBC", "USER", "PASSWORD", '', XO_USETRANS$+XO_GLOBALSHARE$+XO_LOGINDIALOG$+XO_NORESOLVE$)

1))***

hQry=0

FIRST_TIME=1

Steve C.

At 27 NOV 2000 11:45PM w wrote:

Steve –

How about XO_NODIALOG$, rather than XO_DIALOG$.

INET procedures should not open a dialog box.

Can you cache the hXO in a common?

Initialize when you start OI, use it in your INET procedure, close it when you down oi?

Won't prevent crash upon problem login, but shifts it out of the INET procedure.

Hope this helps,

Bob Carten

WinWin Solutions, Inc

At 27 NOV 2000 11:45PM w wrote:

Steve –

How about XO_NODIALOG$, rather than XO_DIALOG$.

INET procedures should not open a dialog box.

Can you cache the hXO in a common?

Initialize when you start OI, use it in your INET procedure, close it when you down oi?

Won't prevent crash upon problem login, but shifts it out of the INET procedure.

Hope this helps,

Bob Carten

WinWin Solutions, Inc

At 27 NOV 2000 11:45PM w wrote:

Steve –

How about XO_NODIALOG$, rather than XO_DIALOG$.

INET procedures should not open a dialog box.

Can you cache the hXO in a common?

Initialize when you start OI, use it in your INET procedure, close it when you down oi?

Won't prevent crash upon problem login, but shifts it out of the INET procedure.

Hope this helps,

Bob Carten

WinWin Solutions, Inc

At 27 NOV 2000 11:45PM w wrote:

Steve –

How about XO_NODIALOG$, rather than XO_DIALOG$.

INET procedures should not open a dialog box.

Can you cache the hXO in a common?

Initialize when you start OI, use it in your INET procedure, close it when you down oi?

Won't prevent crash upon problem login, but shifts it out of the INET procedure.

Hope this helps,

Bob Carten

WinWin Solutions, Inc

At 27 NOV 2000 11:45PM w wrote:

Steve –

How about XO_NODIALOG$, rather than XO_DIALOG$.

INET procedures should not open a dialog box.

Can you cache the hXO in a common?

Initialize when you start OI, use it in your INET procedure, close it when you down oi?

Won't prevent crash upon problem login, but shifts it out of the INET procedure.

Hope this helps,

Bob Carten

WinWin Solutions, Inc

At 27 NOV 2000 11:45PM w wrote:

Steve –

How about XO_NODIALOG$, rather than XO_DIALOG$.

INET procedures should not open a dialog box.

Can you cache the hXO in a common?

Initialize when you start OI, use it in your INET procedure, close it when you down oi?

Won't prevent crash upon problem login, but shifts it out of the INET procedure.

Hope this helps,

Bob Carten

WinWin Solutions, Inc

At 27 NOV 2000 11:45PM w wrote:

Steve –

How about XO_NODIALOG$, rather than XO_DIALOG$.

INET procedures should not open a dialog box.

Can you cache the hXO in a common?

Initialize when you start OI, use it in your INET procedure, close it when you down oi?

Won't prevent crash upon problem login, but shifts it out of the INET procedure.

Hope this helps,

Bob Carten

WinWin Solutions, Inc

At 27 NOV 2000 11:45PM w wrote:

Steve –

How about XO_NODIALOG$, rather than XO_DIALOG$.

INET procedures should not open a dialog box.

Can you cache the hXO in a common?

Initialize when you start OI, use it in your INET procedure, close it when you down oi?

Won't prevent crash upon problem login, but shifts it out of the INET procedure.

Hope this helps,

Bob Carten

WinWin Solutions, Inc

At 27 NOV 2000 11:45PM w wrote:

Steve –

How about XO_NODIALOG$, rather than XO_DIALOG$.

INET procedures should not open a dialog box.

Can you cache the hXO in a common?

Initialize when you start OI, use it in your INET procedure, close it when you down oi?

Won't prevent crash upon problem login, but shifts it out of the INET procedure.

Hope this helps,

Bob Carten

WinWin Solutions, Inc

At 27 NOV 2000 11:45PM w wrote:

Steve –

How about XO_NODIALOG$, rather than XO_DIALOG$.

INET procedures should not open a dialog box.

Can you cache the hXO in a common?

Initialize when you start OI, use it in your INET procedure, close it when you down oi?

Won't prevent crash upon problem login, but shifts it out of the INET procedure.

Hope this helps,

Bob Carten

WinWin Solutions, Inc

At 27 NOV 2000 11:45PM w wrote:

Steve –

How about XO_NODIALOG$, rather than XO_DIALOG$.

INET procedures should not open a dialog box.

Can you cache the hXO in a common?

Initialize when you start OI, use it in your INET procedure, close it when you down oi?

Won't prevent crash upon problem login, but shifts it out of the INET procedure.

Hope this helps,

Bob Carten

WinWin Solutions, Inc

At 27 NOV 2000 11:45PM w wrote:

Steve –

How about XO_NODIALOG$, rather than XO_DIALOG$.

INET procedures should not open a dialog box.

Can you cache the hXO in a common?

Initialize when you start OI, use it in your INET procedure, close it when you down oi?

Won't prevent crash upon problem login, but shifts it out of the INET procedure.

Hope this helps,

Bob Carten

WinWin Solutions, Inc

At 27 NOV 2000 11:45PM w wrote:

Steve –

How about XO_NODIALOG$, rather than XO_DIALOG$.

INET procedures should not open a dialog box.

Can you cache the hXO in a common?

Initialize when you start OI, use it in your INET procedure, close it when you down oi?

Won't prevent crash upon problem login, but shifts it out of the INET procedure.

Hope this helps,

Bob Carten

WinWin Solutions, Inc

At 27 NOV 2000 11:45PM w wrote:

Steve –

How about XO_NODIALOG$, rather than XO_DIALOG$.

INET procedures should not open a dialog box.

Can you cache the hXO in a common?

Initialize when you start OI, use it in your INET procedure, close it when you down oi?

Won't prevent crash upon problem login, but shifts it out of the INET procedure.

Hope this helps,

Bob Carten

WinWin Solutions, Inc

At 27 NOV 2000 11:45PM w wrote:

Steve –

How about XO_NODIALOG$, rather than XO_DIALOG$.

INET procedures should not open a dialog box.

Can you cache the hXO in a common?

Initialize when you start OI, use it in your INET procedure, close it when you down oi?

Won't prevent crash upon problem login, but shifts it out of the INET procedure.

Hope this helps,

Bob Carten

WinWin Solutions, Inc

At 27 NOV 2000 11:45PM w wrote:

Steve –

How about XO_NODIALOG$, rather than XO_DIALOG$.

INET procedures should not open a dialog box.

Can you cache the hXO in a common?

Initialize when you start OI, use it in your INET procedure, close it when you down oi?

Won't prevent crash upon problem login, but shifts it out of the INET procedure.

Hope this helps,

Bob Carten

WinWin Solutions, Inc

At 27 NOV 2000 11:45PM w wrote:

Steve –

How about XO_NODIALOG$, rather than XO_DIALOG$.

INET procedures should not open a dialog box.

Can you cache the hXO in a common?

Initialize when you start OI, use it in your INET procedure, close it when you down oi?

Won't prevent crash upon problem login, but shifts it out of the INET procedure.

Hope this helps,

Bob Carten

WinWin Solutions, Inc

At 27 NOV 2000 11:45PM w wrote:

Steve –

How about XO_NODIALOG$, rather than XO_DIALOG$.

INET procedures should not open a dialog box.

Can you cache the hXO in a common?

Initialize when you start OI, use it in your INET procedure, close it when you down oi?

Won't prevent crash upon problem login, but shifts it out of the INET procedure.

Hope this helps,

Bob Carten

WinWin Solutions, Inc

At 27 NOV 2000 11:45PM w wrote:

Steve –

How about XO_NODIALOG$, rather than XO_DIALOG$.

INET procedures should not open a dialog box.

Can you cache the hXO in a common?

Initialize when you start OI, use it in your INET procedure, close it when you down oi?

Won't prevent crash upon problem login, but shifts it out of the INET procedure.

Hope this helps,

Bob Carten

WinWin Solutions, Inc

At 28 NOV 2000 08:53AM Steve Carlson wrote:

Changing to XO_NODIALOG$ does not prevent XOInstance

from crashing OpenEngine.

Any other suggestions?

Steve C.

At 28 NOV 2000 11:14AM [url=http://www.sprezzatura.com" onMouseOver=window.status=Click here to visit our web site?';return(true)]The Sprezzatura Group[/url] wrote:

Sorry Bob, not too sure we got that…

The Sprezzatura Group

World Leaders in all things RevSoft

View this thread on the forum...

1)
(CRASHES ABOVE
  • third_party_content/community/commentary/forums_nonworks/59a16ce797f5b9e1852569a40054fcd8.txt
  • Last modified: 2023/12/28 07:40
  • by 127.0.0.1