Using !Job in a WoodPecker Script can causes Space Manager to appear to hang
Hint Ref: 021007120011
Hint Date: 12/07/2010
Hint Details:
ISSUE
Within a WookPecker Script, a user wished to run an XML job which in turn ran a report to screen. They wanted the XML Job to wait until the report form was closed by the user, before continuing the job process.
PROBLEM
Within the <ViewReport> tag they set the attribute WAIT to YES, but the result of this was that the report was displayed to screen, but they could not select the report form in order to close it, so the XML job could continue. In addition, they could not 'Cancel' the XML job because it was waiting for the report to close; catch-22.
Setting the WAIT attribute to NO did allow the XML job to continue, but not as a result of the report closing.
SOLUTION
The !Job Woodpecker script command runs the XML job modally. In other words it does not allow control to pass to any other window than the XML job, until the script terminates. The solution is not to run the XML Job modally by using the WoodPecker command !AsyncJob instead.
(Please Note: This Procedure can be destructive and should only be used by Advanced Users. RADical Systems (UK) Limited or its Partners cannot be held responsible, in anyway, for any consequence of using this or any other Database Function, Procedure or SQL command. Responsibility resides solely with the user.
IT IS HIGHLY RECOMMENDED THAT A FULL AND VALID SPACE MANAGER DATABASE BACKUP IS TAKEN AND VERIFIED AS VALID BEFORE MAKING ANY CHANGES TO THE DATABASE.)