Bill, a belated thanks for the advice. Your tip is appreciated at 2 levels. It is an approach to debugging/tracing that I had not tried. Additionally, I suspect that it is a subtle, oh-so-polite, and positive encouragement from you to me about gettin' my butt to an SAT training class, where I'm sure that things like this are but one of many topics covered. Well, believe me, it's still on my mind to do so, and then, to do it in Indy.
I really appreciate your willingness to share and your gentlemanly courtesy. Steve From: [email protected] [mailto:[email protected]] On Behalf Of Bill Downall Sent: Friday, February 27, 2009 5:43pm 17:43 To: RBASE-L Mailing List Subject: [RBASE-L] - Re: &vCommand Issues in Form Control EEP? Steve, They work fine. I have a form that builds a hundred property commands in &vcommand variables and executes them without problem. Be careful that quotation marks are in the right places and the right numbersin your &vcommand variables. And create a panel on your form with the component ID debugPanel, and locate the variable vCommand on it. Make it invisible on startup, and in your on after start eep, do this: IF (cval('trace')) = 'ON' THEN PROPERTY debugpanel VISIBLE 'true' ELSE property debugpanel VISIBLE 'false' ENDIF Then when you are tracing through your form, you can see it, and any other variables you put there. Bill On Fri, Feb 27, 2009 at 6:32 PM, Wills, Steve <[email protected]> wrote: In an EEP associated with a Variable Checkbox control, is it allowable to build a command string, assign it to a variable, vCommand, then execute it in the control's OnClick EEP with the statement &vCommand? I am doing this and, so far, everything seems to be working in the EEP and form. However, every time I click, I do get an "Information" dialog saying "Unrecognized command in Entry/Exit Procedure.". However, as I said, everything appears to function as want it to. Any ideas? Thanks, Steve in Memphis
