You have to be careful to not exceed the length limit on the string containing the "Select", so in this location I would Definitely use the short version of RBase commands and keep the table and col names shorties as well....
----- Original Message ----- From: "David M. Blocker" <[EMAIL PROTECTED]> To: "RBG7-L Mailing List" <[email protected]> Sent: Sunday, April 24, 2005 11:40 AM Subject: [RBG7-L] - Re: Running R:BASE Your Way! (Part 9) > Cool, Mike!! > > David > > David Blocker > [EMAIL PROTECTED] > 781-784-1919 > Fax: 781-784-1860 > Cell: 339-206-0261 > ----- Original Message ----- > From: "MikeB" <[EMAIL PROTECTED]> > To: "RBG7-L Mailing List" <[email protected]> > Sent: Sunday, April 24, 2005 8:43 AM > Subject: [RBG7-L] - Re: Running R:BASE Your Way! (Part 9) > > >> >> ----- Original Message ----- >> From: "A. Razzak Memon" <[EMAIL PROTECTED]> >> To: "RBG7-L Mailing List" <[email protected]> >> Sent: Saturday, April 23, 2005 10:59 PM >> Subject: [RBG7-L] - Running R:BASE Your Way! (Part 9) >> >> <snip> >> > . You still need the external EEPs if running your code >> > as Table "On Row Entry", "On Row Exit", "After Saving >> > Row" and "After Leaving Section". >> >> </snip> >> >> >> Well, maybe Not! ... Even though the eeps wouldn't be hidden in the form >> description, they can be stored in a table in the database as a type > VarChar... >> A few months back I posted an example of this. >> >> Basically, in the edit box for the particular Table level EEP, you type > code >> such as this.. >> >> Select VarCharData From SomeTable wher ColumnWithUniqueCommandName = >> 'TheCommandToRun' >> >> >> It appears that whatever text is in the edit box is passed to RBase "RUN" >> command, so the command executes.. NO External EEPs! >> >> >
