That's exactly it - and it's from Razzak's programming standards. For more examples, see the NewStuff.rmd file in the NewStuff sample programs that shipped with version 6.5++.
There are a lot of variations on how you could do this same thing, depending on your exact purpose. Sami ----- Original Message ----- From: "J. Stephen Wills" <[EMAIL PROTECTED]> To: "RBASE-L Mailing List" <[EMAIL PROTECTED]> Sent: Wednesday, November 19, 2003 10:28 AM Subject: [RBASE-L] - Re: Trapping Form Events ... > Sami, thanks. I think what you describe is super, but it might be a bit > more than I need for this particular issue, at least as I began to pare > things down to the most essential functionality I require. However, just to > be sure I understand, is what your describing here a means for enumerating > the different events/methods, as might done implicitly in VB/Delphi/C++? > > For example, assume that I have a button that says "EXIT" with BTN_EXIT.CMD > attached to it. Having, as you indicated : > > > SET VAR fButton INTEGER = 0 > > prior to form entry, then my BTN_EXIT.CMD could : > > > SET VAR fButton = 99 > > Then, if the user clicked the "EXIT" button, the value of 99 for fButton > would "tell" me that they clicked the "EXIT" button. If it were still 0, > then, as this is still the pre-entry value, I know that they left the form > by clicking the [X] or perhaps some other means, but not by choosing one of > the eep-enabled form objects. Is this a (more-or-less) correct > understanding? > > Thanks, > Steve in Memphis > > ----- Original Message ----- > From: "Sami Aaron" <[EMAIL PROTECTED]> > To: "RBASE-L Mailing List" <[EMAIL PROTECTED]> > Sent: Tuesday, November 18, 2003 1:35 PM > Subject: [RBASE-L] - Re: Trapping Form Events ... > > > > Steve - > > > > You can define a variable, fButton, prior to opening the form; > > > > SET VAR fButton INTEGER = 0 > > EDIT USING formanme WHERE yada yada > > > > Then on any other methods you give the user to exit the form, you add the > > following line to your EEP: > > > > SET VAR fButton = 1 (or anything other than 0) > > > > If the user clicks the "X" to exit, fButton remains set at 0, otherwise it > > 's set to a different number, depending on your program. Then in your > > calling program, you can check the value of fButton after the EDIT USING > > statement. > > > > IF fButton = 0 THEN > > ... > > ELSE > > .. > > ENDIF > > > > Let me know if you need a more detailed explaination. > > > > Sami > > > > ----------------------------------------------------------------- > > Sami Aaron > > Software Management Specialists > > 19312 W 63rd Terr > > Shawnee KS 66218 > > mailto:[EMAIL PROTECTED] > > 913-915-1971 > > > > ----- Original Message ----- > > From: J. Stephen Wills > > To: RBASE-L Mailing List > > Sent: Tuesday, November 18, 2003 1:02 PM > > Subject: [RBASE-L] - Trapping Form Events ... > > > > > > Is it possible in RBWINv6.5++ to trap at the form-level whether or not the > > form was closed by clicking on the [X] button? > > > > I am trapping LASTKEY at the field-level, but, in this situation, a logon, > I > > also would like to trap that [X] and handle like a field-level [ESC]. > > > > > > Thanks, > > Steve in Memphis > > > > > >
