Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
CALL Statement | ||||||||
Line: 7 to 7 | ||||||||
| ||||||||
Added: | ||||||||
> > | After further review, it was decided that no checking will be done by the CALL statement, therefore there are no changes to CALL for unicode. | |||||||
Test PlanDo non UNICODE or NATIONAL arguments still work correctly? | ||||||||
Line: 16 to 18 | ||||||||
Does the CALL statement itself allow for UNICODE or NATIONAL fields to define the call function name?
BUGS | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
-- JeanNeron - 2011-03-09 \ No newline at end of file |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
CALL Statement | ||||||||
Line: 16 to 16 | ||||||||
Does the CALL statement itself allow for UNICODE or NATIONAL fields to define the call function name?
BUGS | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
-- JeanNeron - 2011-03-09 |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Added: | ||||||||
> > |
CALLExpected Behaviour
BUGS
|