I have changed my form and the eep so that they follow the "standard" way of
using multiple buttons and the eep is no longer codelocked.
My first impression is a significant improvement in that the number of
crashes has decreased when the app is run without the pause before calling
the form.
I have made it crash twice but I was trying my hardest to do so by quitting
and running R:Base again as quickly as I could. Previously this would have
been easy.
So, why does this EEP work in plain text:
SET VAR vButton = .%1
SET VAR vSelName TEXT = NULL
SWITCH .vButton
CASE 'G'
SET VAR vSelName = 'GENERAL'
BREAK
...
CASE 'X'
SET VAR vSelName = 'EXIT'
BREAK
ENDSW
EXITFORM
RETURN
with button command: Run xxx.EEP USING x
whereas this, codelocked, _sometimes_ doesn't:
$COMMAND
General
SET VAR vSelName = 'GENERAL'
EXITFORM
RETURN
...
$COMMAND
SysExit
SET VAR vSelName = 'EXIT'
EXITFORM
RETURN
with button command: Run xxx IN xxx.EEP
Regards,
Alastair.
----- Original Message -----
From: "Alastair Burr" <[EMAIL PROTECTED]>
To: "RBASE-L Mailing List" <[EMAIL PROTECTED]>
Sent: Tuesday, January 14, 2003 12:15 AM
Subject: [RBASE-L] - Re: CriteriaForMyUnstablenessWithR:Base6.5++Build 1.862
> Following Razzak's message I've checked the History demo and can see what
I
> presume is RBTI's "standard" method of using multiple buttons is what
Javier
> pointed out just beforehand. It's getting late here now so I'll try that
> tomorrow.
>
> Just for the record, the problem is not that I can't get the buttons to
work
> with my eep - they work fine - once I get into the form. R:Base sometimes
> crashes or hangs just before getting into the form. I'd be happy to use
the
> "standard" method but all I suggested was that _maybe_ my codelocked eep
was
> the problem _if_ it had some sort of error that R:Base was finding as it
> entered the form.
>
> My eep may not be the best way and I'm happy to change it to see if that
> stops the crashes.
