B
Bernard Ashton
Guest
When I use the usual PROMPT-FOR in a compiled procedure nothing happens when the .r is run within the .Net GUI environment, the program ends without doing anything or any messages appearing. It runs correctly when run as a .p and requests the Job Number.
The relevant part of the code is:
DEFINE VARIABLE lvJobNo AS CHARACTER FORMAT "X(10)".
DO WHILE TRUE:
PROMPT-FOR lvJobNo LABEL "Job Number for Job Costing Extract".
ASSIGN lvJobNo = INPUT lvJobNo.
IF lvJobNo = "" THEN
DO:
MESSAGE "Job No empty - finishing" VIEW-AS ALERT-BOX.
RETURN.
END.
. . .
END.
What needs to happen to make it work in .NET GUI?
Continue reading...
The relevant part of the code is:
DEFINE VARIABLE lvJobNo AS CHARACTER FORMAT "X(10)".
DO WHILE TRUE:
PROMPT-FOR lvJobNo LABEL "Job Number for Job Costing Extract".
ASSIGN lvJobNo = INPUT lvJobNo.
IF lvJobNo = "" THEN
DO:
MESSAGE "Job No empty - finishing" VIEW-AS ALERT-BOX.
RETURN.
END.
. . .
END.
What needs to happen to make it work in .NET GUI?
Continue reading...