If you want to use one (non codelocked) eep to support many buttons, you can
use the following code:
FORMS - Under EEP or Commnad block for the first button use:
test_eep_name.eep USING A
for the next button use:
test_eep_name.eep USING B
and so on...
the eep test_eep_name.eep will look like this:
==============================================
*(
test_eep_name.eep - eep used to support many buttons
)
SET VAR vopt1 = .%1
SWITCH .vopt1
CASE 'A'
-- do whatever you need your eep to do for the first button
BREAK
CASE 'B'
-- do whatever you need your eep to do for the second button
BREAK
ENDSW
RETURN
==============================================
If you want, you can codelock the eep and the you would use:
Under EEP or Command block for the button use:
Run test_eep_name in test_eep_name.apx using A
( I used the extension "apx" for codelocked files )
And so on...
I hope this information is of help.
Javier,
Javier Valencia, PE
President
Valencia Technology Group, L.L.C.
14315 S. Twilight Ln., Suite #14
Olathe, KS 66062-4571
(913)829-0888
(913)649-2904 FAX
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Ben Petersen
Sent: Sunday, January 12, 2003 5:39 PM
To: RBASE-L Mailing List
Subject: [RBASE-L] - Re: Fw: [RBASE-L] - Fw: [RBASE-L] - Re:
CriteriaForMyUnstablenessWithR:Base6.5++Build 1.862
> Any thoughts on what systems? Is there something common?
I haven't been able to run down the similarities. The clients are
remote and incapable of describing their equipment. Tech support
ranges from excellent to hostile.
> I'll try some other commands in place of the pause but
> I tend to have blank lines in my code to simplify the layout
> so I doubt they'll make any difference (but I'll still try!).
fwiw my code has lots of white space also.
> I tried originally to run the eep as ascii but I get the error that it
> is not a run command.
The field that specifies the eep should only contain the file name.
The file itself should look like this:
> SET VAR vSelName = 'GENERAL'
> EXITFORM
> RETURN
No $Command; No Block Name
> There's almost a dozen of these in the eep and
> nothing more (bar some comments at the end
> after the last return)
Do I understand... a dozen buttons that execute different command
blocks? I have no idea if this is better... _maybe_ easier to
maintain (Same eep for all 12 buttons):
--AlsEep.eep
-------------------
SET V zFldNm = (CVAL('form_field_name'))
Switch (.zFldNm)
Case 'General'
SET VAR vSelName = 'GENERAL'
Break
Case
Break
....
EndSw
ExitForm
Return
------------------------
Of course if vSelName is always the text on the button you can
forget the switch block and:
SET V vSelName = (CVAL('form_field_name'))
ExitForm
Return
Ben Petersen
On 12 Jan 2003, at 23:42, Alastair Burr wrote:
> Ben,
>
> Any thoughts on what systems? Is there something common? I'll try some
> other commands in place of the pause but I tend to have blank lines in
> my code to simplify the layout so I doubt they'll make any difference
> (but I'll still try!).
>
> I tried originally to run the eep as ascii but I get the error that it
> is not a run command. There's almost a dozen of these in the eep and
> nothing more (bar some comments at the end after the last return):
>
> $COMMAND
> General
> SET VAR vSelName = 'GENERAL'
> EXITFORM
> RETURN
>
> In this example, clicking on the General button runs this $Command in
> the eep. The app then uses the variable to continue. It could hardly
> be simpler - but I dare say someone knows a better way?
>
> Regards,
> Alastair.
>
>
> ----- Original Message -----
> From: "Ben Petersen" <[EMAIL PROTECTED]>
> To: "RBASE-L Mailing List" <[EMAIL PROTECTED]>
> Sent: Sunday, January 12, 2003 1:28 PM
> Subject: [RBASE-L] - Re: Fw: [RBASE-L] - Fw: [RBASE-L] - Re:
> CriteriaForMyUnstablenessWithR:Base6.5++Build 1.862
>
>
> > I _think_ there are two issues, and they only occur on certain
> > systems it seems. In one instance pausing helps, like you say, it
> > seems to give RB a chance to finish something. In the other, in my
> > _apx_ files, adding an unnecessary command or even blank lines
> > solves the problem (and, again, only needed on some systems). I
> > don't codelock my eeps yet... maybe try running yours as native
> > ascii?
> >
> > Ben Petersen
> >
> >
> >
> >
> > On 12 Jan 2003, at 8:03, Alastair Burr wrote:
> >
> > > Hi Ben,
> > >
> > > No _without_ the pause it crashes or hangs.
> > >
> > > It _seems_ as if my system needs a moment or two to think about
> > > what it's going to do. It _seems_ as if rushing straight into the
> > > form causes the problem. There is an eep on the form but it only
> > > runs when a button is clicked.
> > >
> > > Thinking aloud and without any forethought for a moment:
> > >
> > > Does it? Maybe R:Base "mentally" runs/scans the eep on entry
> > > rather like it knows there's no endwhile in a loop if it's
> > > missing.
> > >
> > > This is the only eep that I have which is codelocked. It seems to
> > > have to be codelocked because I need to use the "run [command] in
> > > [eep]" syntax on the buttons.
> > >
> > > Is this a possibility?
> > > Anybody got any thoughts on what might cause a codelocked eep to
> > > hiccup rather than a plain ascii one? I thinks that it's very
> > > simple but I'll check it now anyhow.
> > >
> > > Regards,
> > > Alastair.
> > >
> > >
> > >
> > >
> > > ----- Original Message -----
> > > From: "Ben Petersen" <[EMAIL PROTECTED]>
> > > To: "RBASE-L Mailing List" <[EMAIL PROTECTED]>
> > > Sent: Sunday, January 12, 2003 12:01 AM
> > > Subject: [RBASE-L] - Re: Fw: [RBASE-L] - Fw: [RBASE-L] - Re:
> > > CriteriaForMyUnstablenessWithR:Base6.5++Build 1.862
> > >
> > >
> > > > > When I remove the comment from the pause I get the crashes.
> > > >
> > > > You mean if you _allow_ the pause it crashes???
> > > >
> > > > Have you tried adding blank lines at about that point? Or
> > > > nonsense commands (Unnecessary select or something). I just did
> > > > this again for a routine that runs everywhere but Hawaii
> > > > (again). I wonder if your system has something in common with
> > > > theirs?
> > > >
> > > > Ben Petersen
> > > >
> > > >
> > > > On 12 Jan 2003, at 7:30, Alastair Burr wrote:
> > > >
> > > > > The original posting of this got a non-delivery messages so
> > > > > I'll try again.
> > > > >
> > > > > Regards,
> > > > > Alastair.
> > > > >
> > > > >
> > > > > ----- Original Message -----
> > > > > From: "Alastair Burr" <[EMAIL PROTECTED]>
> > > > > To: <[EMAIL PROTECTED]>
> > > > > Sent: Wednesday, January 08, 2003 6:33 PM
> > > > > Subject: Re: [RBASE-L] - Fw: [RBASE-L] - Re:
> > > > > CriteriaForMyUnstablenessWithR:Base6.5++Build 1.862
> > > > >
> > > > >
> > > > > > JM,
> > > > > >
> > > > > > I've just put CrashGuard back in so I don't get the Windows'
> > > > > > error message at the moment but it was the standard "illegal
> > > > > > operation" one 3 times
> > > > > every
> > > > > > crash.
> > > > > >
> > > > > > The data from CrashGuard is this:
> > > > > >
> > > > > > Windows 98 Version 4.10.2222
> > > > > > RBG65.EXE caused fault #c0000005 in RBG65.EXE at address
> > > > > > 0187:0071baa7
> > > > > >
> > > > > > Registers:
> > > > > > EAX=01b7f0f0 CS=0187 EIP=0071baa7 EFLGS=00010293
> > > > > > EBX=00b8e684 SS=018f ESP=00b8e634 EBP=00b8e64c
> > > > > > ECX=01b3ea98 DS=018f ESI=000066a6 FS=6cdf
> > > > > > EDX=00b8e684 ES=018f EDI=00000000 GS=0000
> > > > > >
> > > > > > Bytes at CS:EIP:
> > > > > > ff 77 08 e8 24 44 00 00 83 c4 0c 89 45 fc 83 7d
> > > > > >
> > > > > > Stack dump:
> > > > > > 00000000 00000002 00b8f03c 00000002 00001000 01b3ea98
> > > > > > 00b8f3b0 004c48da 01b7f0f0 000066a6 00000000 00b8e684
> > > > > > 0077b5ad 01b87864 00755698 01ae236c
> > > > > >
> > > > > > This is the command file just prior to calling the form:
> > > > > >
> > > > > > CONNECT MULTIjpg
> > > > > > CREATE TEMP TABLE `ToDo` +
> > > > > > (`Things` TEXT (60), +
> > > > > > `EntryDate` DATETIME )
> > > > > > RUN ToDo.DAT -- created earlier and working!
> > > > > >
> > > > > > SET CAPTION 'Multi-Database Selector & Things To Do'
> > > > > > SET NULL '-0- '
> > > > > > SET NULL ' '
> > > > > > SET VAR vSelName = NULL
> > > > > >
> > > > > > -- pause for 2
> > > > > >
> > > > > > LABEL lMainMenu
> > > > > > -- CLS
> > > > > > -- CLS FROM 15, 24 TO 17, 76 WHITE
> > > > > > -- WRITE 'Please wait while the databases are
> > > > > > initialised...' AT 16, 25 LIGHT RED ON WHITE -- RHIDE --
> > > > > > EDIT USING Selector CAPTION 'Click on an image or a button
> > > > > > to
> > > > > choose...'
> > > > > >
> > > > > > EDIT MDI Selector AS Selector AT 65,290,1230,717 +
> > > > > > CAPTION 'Click on an image or a button to choose...'
> > > > > > ----------
> > > > > >
> > > > > > The commands prior to the above obtain the data from another
> > > > > > database and the connect here is the first time that this
> > > > > > database is opened and this form used. Nothing appears to be
> > > > > > wrong at all before this point. Either version of edit using
> > > > > > crashes R:Base sometimes with to choose
> > > > > between
> > > > > > them.
> > > > > > When I remove the comment from the pause I get the crashes.
> > > > > >
> > > > > > Regards,
> > > > > > Alastair.
> > > > > >
> > > > > >
> > > > > > ----- Original Message -----
> > > > > > From: "J.M. GRATIAS" <[EMAIL PROTECTED]>
> > > > > > To: "RBASE-L Mailing List" <[EMAIL PROTECTED]>
> > > > > > Sent: Wednesday, January 08, 2003 3:08 PM
> > > > > > Subject: [RBASE-L] - Fw: [RBASE-L] - Re:
> > > > > > CriteriaForMyUnstablenessWithR:Base6.5++Build 1.862
> > > > > >
> > > > > >
> > > > > >
> > > > > > Allastair :
> > > > > >
> > > > > > >>
> > > > > > The problem was that it didn't crash every time. Some days
> > > > > > were worse than others but I'd guess about 25-50% of the
> > > > > > time it crashed without the 2 second pause. Much less rarely
> > > > > > it crashed even with the pause. <<
> > > > > >
> > > > > > Your problem looks very close as mine, except I didn't try
> > > > > > PAUSE. What message do you get before crash ?
> > > > > >
> > > > > >
> > > > > > >>
> > > > > > Since changing the buttons to text I haven't had a crash at
> > > > > > all. <<
> > > > > >
> > > > > > That's interresting : nearly all my forms has severals
> > > > > > graphics BMP buttons. As far as I can remember, I never had
> > > > > > problems with the few forms that has only text buttons.
> > > > > >
> > > > > >
> > > > > > >>
> > > > > > As far as the PC is concerned I'm doing everything now with
> > > > > > W98SE that I was before with the exception of having
> > > > > > Crashguard running. <<
> > > > > >
> > > > > > That's a big difference with me : no problem with W98SE.
> > > > > > Problem only with NT/W2K.
> > > > > >
> > > > > >
> > > > > > >>
> > > > > > Probably tomorrow I'll rebuild the database from a restore
> > > > > > and the form from scratch without any images. It will then
> > > > > > be interesting to see what
> > > > > happens
> > > > > > when I put the images back on the form on a copy of the new
> > > > > > database!
> > > > > > <<
> > > > > >
> > > > > > Let us know ....
> > > > > >
> > > > > > J.M. GRATIAS, Logimatique
> > > > > >
> > > > >
> > > >
> > >
> >
>
