>>Local should work, but in case there may be problems, you can declare variables private.
>
>Basically it all depends on in what context the REPORT FORM command is executing. If it operates within the context of the method/procedure in which it is executed, then the variable will be "visible". Declaring them to be PRIVATE would be more likely to work than LOCAL -- I would lean toward using PRIVATE to allow for the possibility of a pre-processing or post-processing stage (in which case, a new call level would likely occur -- causing the LOCAL variables to become hidden).

And then there's the issue of all the code snippets within the report, which may want to use some of these variables. My hunch is that they wouldn't see the locals.