Alaska Software Inc. - QUIT command generate error
Username: Password:
AuthorTopic: QUIT command generate error
Jorge LQUIT command generate error
on Fri, 11 Dec 2009 09:03:36 -0300
Hi All, i don´t understand why QUIT command generate recursive error

i write bad this line when test AUX where is NIL

  If ( Len( M->AUX ) >= nELEM .And. M->AUX != NIL .And. Len( M->AUX[nELEM] ) 
 >= 10 )

this is the trace 
Procedure _QUIT( nErrorLevel )
................... 
nErrorLevel :=If( ValType( nErrorLevel ) = 'N', nErrorLevel, 0 )
_QUIT(592) 
dbCloseAll()
_QUIT(592) 
ErrorLevel( nErrorLevel )
_QUIT(592) 
QUIT
STANDARD_EH(524) 
Return
(B)ERRORSYS@0000(43)
XCHO2400(803)
ABROWSE(101)
ALL2400(661)
MINIBROW(129)
MENU2400(43)
MENUBD00(23)
MENUB000(40)
MENU0000(106)
DEPOSITO(350)
MAIN(86)
Call Stack of GUI Thread (648):
Call Stack of Thread 3 (1340):
DELARRAY(140)
\\Servidor\datos\MORON\WNORMAL.EXE
TimeStamp: 20091210 20:15
End of FATAL ERROR LOG.


thanks and regards
Regan Cawkwell Re: QUIT command generate error
on Fri, 11 Dec 2009 12:54:14 +0000
I would do the M->AUX != NIL test before using len(M->AUX) at the very least...

Regan Cawkwell
Company  : Real Business Applications Ltd
Title    : Technical Support
Websites : www.rbauk.com
Email    : regan@rbauk.com
------------------------------------------------------

On 11/12/2009 12:03pm, Jorge L wrote:
> Hi All, i don´t understand why QUIT command generate recursive error
>
> i write bad this line when test AUX where is NIL
>
> If ( Len( M->AUX ) >= nELEM .And. M->AUX != NIL .And. Len( M->AUX[nELEM]
> ) >= 10 )
>
> this is the trace Procedure _QUIT( nErrorLevel )
> .................... nErrorLevel :=If( ValType( nErrorLevel ) = 'N',
> nErrorLevel, 0 )
> _QUIT(592) dbCloseAll()
> _QUIT(592) ErrorLevel( nErrorLevel )
> _QUIT(592) QUIT
> STANDARD_EH(524) Return
> (B)ERRORSYS@0000(43)
> XCHO2400(803)
> ABROWSE(101)
> ALL2400(661)
> MINIBROW(129)
> MENU2400(43)
> MENUBD00(23)
> MENUB000(40)
> MENU0000(106)
> DEPOSITO(350)
> MAIN(86)
> Call Stack of GUI Thread (648):
> Call Stack of Thread 3 (1340):
> DELARRAY(140)
> \\Servidor\datos\MORON\WNORMAL.EXE
> TimeStamp: 20091210 20:15
> End of FATAL ERROR LOG.
>
>
> thanks and regards
>
Jorge LRe: QUIT command generate error
on Fri, 11 Dec 2009 13:21:53 -0300
>I would do the M->AUX != NIL test before using len(M->AUX) at the very 
>least...

yes.....

but, the question is why quit generate error  ?
why QUIT not abend the program when it execute? (and generate error)
PD i havent exit procedures

"Regan Cawkwell" <regan@rbauk.com> escribió en el mensaje de noticias 
news:3f3ccd6c$38cd9e60$4ae86@news.alaska-software.com...
>I would do the M->AUX != NIL test before using len(M->AUX) at the very 
>least...
>
> Regan Cawkwell
> Company  : Real Business Applications Ltd
> Title    : Technical Support
> Websites : www.rbauk.com
> Email    : regan@rbauk.com
> ------------------------------------------------------
>
> On 11/12/2009 12:03pm, Jorge L wrote:
>> Hi All, i don´t understand why QUIT command generate recursive error
>>
>> i write bad this line when test AUX where is NIL
>>
>> If ( Len( M->AUX ) >= nELEM .And. M->AUX != NIL .And. Len( M->AUX[nELEM]
>> ) >= 10 )
>>
>> this is the trace Procedure _QUIT( nErrorLevel )
>> .................... nErrorLevel :=If( ValType( nErrorLevel ) = 'N',
>> nErrorLevel, 0 )
>> _QUIT(592) dbCloseAll()
>> _QUIT(592) ErrorLevel( nErrorLevel )
>> _QUIT(592) QUIT
>> STANDARD_EH(524) Return
>> (B)ERRORSYS@0000(43)
>> XCHO2400(803)
>> ABROWSE(101)
>> ALL2400(661)
>> MINIBROW(129)
>> MENU2400(43)
>> MENUBD00(23)
>> MENUB000(40)
>> MENU0000(106)
>> DEPOSITO(350)
>> MAIN(86)
>> Call Stack of GUI Thread (648):
>> Call Stack of Thread 3 (1340):
>> DELARRAY(140)
>> \\Servidor\datos\MORON\WNORMAL.EXE
>> TimeStamp: 20091210 20:15
>> End of FATAL ERROR LOG.
>>
>>
>> thanks and regards
>>
>
Regan Cawkwell Re: QUIT command generate error
on Fri, 11 Dec 2009 16:47:14 +0000
Ah, Ok.

I thought the code was from a function of yours called _QUIT that was being called within 
your errorblock.

Regan Cawkwell
Company  : Real Business Applications Ltd
Title    : Technical Support
Websites : www.rbauk.com
Email    : regan@rbauk.com
------------------------------------------------------

On 11/12/2009 04:21pm, Jorge L wrote:
>> I would do the M->AUX != NIL test before using len(M->AUX) at the
>> very least...
>
> yes.....
>
> but, the question is why quit generate error ?
> why QUIT not abend the program when it execute? (and generate error)
> PD i havent exit procedures
>
> "Regan Cawkwell" <regan@rbauk.com> escribió en el mensaje de noticias
> news:3f3ccd6c$38cd9e60$4ae86@news.alaska-software.com...
>> I would do the M->AUX != NIL test before using len(M->AUX) at the
>> very least...
>>
>> Regan Cawkwell
>> Company : Real Business Applications Ltd
>> Title : Technical Support
>> Websites : www.rbauk.com
>> Email : regan@rbauk.com
>> ------------------------------------------------------
>>
>> On 11/12/2009 12:03pm, Jorge L wrote:
>>> Hi All, i don´t understand why QUIT command generate recursive error
>>>
>>> i write bad this line when test AUX where is NIL
>>>
>>> If ( Len( M->AUX ) >= nELEM .And. M->AUX != NIL .And. Len( M->AUX[nELEM]
>>> ) >= 10 )
>>>
>>> this is the trace Procedure _QUIT( nErrorLevel )
>>> .................... nErrorLevel :=If( ValType( nErrorLevel ) = 'N',
>>> nErrorLevel, 0 )
>>> _QUIT(592) dbCloseAll()
>>> _QUIT(592) ErrorLevel( nErrorLevel )
>>> _QUIT(592) QUIT
>>> STANDARD_EH(524) Return
>>> (B)ERRORSYS@0000(43)
>>> XCHO2400(803)
>>> ABROWSE(101)
>>> ALL2400(661)
>>> MINIBROW(129)
>>> MENU2400(43)
>>> MENUBD00(23)
>>> MENUB000(40)
>>> MENU0000(106)
>>> DEPOSITO(350)
>>> MAIN(86)
>>> Call Stack of GUI Thread (648):
>>> Call Stack of Thread 3 (1340):
>>> DELARRAY(140)
>>> \\Servidor\datos\MORON\WNORMAL.EXE
>>> TimeStamp: 20091210 20:15
>>> End of FATAL ERROR LOG.
>>>
>>>
>>> thanks and regards
>>>
>>
>
>