Programming Guide - Actian

OpenROAD Names• Although you can use a nullable variable as a dynamic name, the variablecannot contain a null when it is used in an SQL statement or a 4GLstatement because the null causes a runtime error.The statement that contains the error may be executed, but the valueused in place of the variable is zero if a number is expected or“$NULL$ERROR” if a character string is expected, which may cause aruntime error.• When using dynamic names that are specified statically, do not putquotation marks around the name unless the name is identical to anOpenROAD word.For more information, see the Language Reference Guide online help for alist of these reserved 4GL keywords.• When using dynamic names that are specified dynamically, specify avarchar variable.At runtime, OpenROAD substitutes the current value of the variable for thename.The advantage of using a dynamically-specified dynamic name is that thevalues can be substituted at runtime. This behavior allows processing to beguided by user input or other runtime conditions.Name ResolutionOpenROAD application components share the same name space. This meansthat OpenROAD identifies the component strictly by name and does notconsider the context in which the name is used. These components are:• Variables• Named constants• Frames• Procedures• ClassesWhen OpenROAD encounters a name, it uses the first component it finds thatmatches the name. The context in which the name is specified has no effect onthe name resolution. For example, when you use a procedure name in acallproc statement, OpenROAD searches for any component with that name,not just a procedure.OpenROAD searches for names in the following order:1. Current event block, local procedure, or user class method2. Current field scriptLanguage Elements 21