I still like the -- comment syntax better because it is easier to find the end of the comment. Also RSTYLE does not touch -- comments which is the desired behavior.
In RBEDIT highlight a block of code You can right click - block - comment or uncomment the block Dennis McGrath -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Dennis McGrath Sent: Monday, November 09, 2009 1:28 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Unknown Entry/Exit Procedure Error *{} is C syntax {} is RBASE syntax Dennis -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Thomas Eldred Sent: Monday, November 09, 2009 1:23 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Unknown Entry/Exit Procedure Error I thought you had to use *{} --- should it just be {} because I do see that if I remove the comments the error vanishes....but it is not picked up in code check and it is how I have been commenting since I heard it was possible to include parends in that manner. tom -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Alastair Burr Sent: Monday, November 09, 2009 1:49 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Unknown Entry/Exit Procedure Error Looks like curly brackets around the remmed commands but you start them with an * as well. Regards, Alastair. -------------------------------------------------- From: "Thomas Eldred" <[email protected]> Sent: Monday, November 09, 2009 6:33 PM To: "RBASE-L Mailing List" <[email protected]> Subject: [RBASE-L] - Unknown Entry/Exit Procedure Error > Good Afternoon all, > > I am getting an "Unrecognized command in Entry/Exit Procedure" Error" when > clicking a Bit Button and then again when exiting from the procedure > inside > the button. > > Everything works in the routine -- that is it does its job, but I cannot > find the source of this notice. The form holding the button has no eeps on > start, before, after, etc... and neither does the form being called when > the > button is pushed. > > I feel I have isolated that it is something to do with the button, being > that the notice is not presented until it is clicked. The code for the > button is below... > > Anyone who could provide a clue? > > Thank you > > Tom Eldred > > > > The code for the button is: > > --get rush number > SET VARIABLE voldpin INTEGER = 0 > SET VARIABLE vnewpin INTEGER = 0 > SET VARIABLE vrushnum INTEGER = NULL > -- 0 means 'no' > SELECT rushnum INTO vrushnum FROM people WHERE idnum = .vidnum > > LABEL rushnumber > IF vrushnum IS NULL THEN > GOTO newmem > ENDIF > GOTO contribution > > LABEL newmem > SET VAR vrushnum INTEGER = NULL > SET VAR vhighrush INTEGER = NULL > SELECT MAX(rushnum) INTO vhighrush FROM people > SET VARIABLE vrushnum = (.vhighrush + 1) > UPDATE people SET rushnum = .vrushnum WHERE idnum = .vidnum > EDIT USING newrushmem > GOTO contribution > > LABEL contribution > *{SELECT pinnumber INTO voldpin FROM rushtrans + > WHERE contransid IN (SELECT MAX(contransid) FROM rushtrans + > WHERE rushnum = .vrushnum) > > SELECT donortotal INTO voldtotal FROM rushcontview + > WHERE datelast = (SELECT MAX (contirbdate) FROM rushtrans + > WHERE rushnum = .vrushnum)} > > SET ERROR MESSAGE 2418 OFF > INSERT INTO rushtrans (rushnum, pinnumber, processdate) VALUES (.vrushnum, > + > .voldpin, .#DATE) > EDIT USING rushcont WHERE rushnum = .vrushnum AND processdate = .#DATE > > > *{SELECT pinnumber INTO vnewpin FROM rushtrans + > WHERE contransid IN (SELECT MAX(contransid) FROM rushtrans + > WHERE rushnum = .vrushnum) > UPDATE rushtrans SET pinnumber = .vnewpin + > WHERE rushnum =.vrushnum AND processdate = .#DATE} > SET ERROR MESSAGE 2418 ON > RETURN > > > > No virus found in this incoming message. > Checked by AVG - www.avg.com > Version: 9.0.698 / Virus Database: 270.14.56/2491 - Release Date: 11/09/09 > 07:39:00 >
