I have converted a v7.7.05-created HTML form to v8.1.04 (i.e., I have simply opened the form in the HTML Canvas and let App Studio do its thing). When I run the form, it presents itself looking pretty much like it did in v7.7.05 (whew!), but when I click the "run" button, the associated (external) report procedure is being executed TWICE. Ideas?

Craig

This message has been edited. Last edited by: Craig R.,

Did you look at your tasks? I have seen it where I have had the same task assigned twice somehow.

Thanks, MattC, but it doesn't appear to me that they're in there twice.

Craig

Have you tried commenting out the OnExecute line in the javascript that was put there in the 7.7 release?

Rob:

I think you're onto something here! Yes, I did comment-out the OnExecute line and the report did only execute once. But now I'm noticing that if my validation code that's in the run button's click event catches an error and issues an alert, the "return;" following the alert doesn't stop the report from running! I'm new to v8, so can you tell me how to "derail" a procedure from executing if you decide, in code, that it shouldn't?

Thanks,

Craig

You will need to have two buttons.

The first button would be attached to run the focexec. You would then hide this button on the page.

The second button would be used to run your validation function. Your validation function, when passed, would then fire the click event on the first button.

This is the only way that I know to do your own validation at this time.

Create a javascript function that if it is false will return a value other than 0. For example:


function myTest()
if (fromDate > toDate){
alert("From date(" + dateFrom + ") must be less than To date(" + dateTo + ")");
return (2);
}
return (0);
}



In your Tasks & Animations the task that isassociated with the run button - say 'Task 2' - make a javascript call to 'myTest' - then add the additional task under it to run the report.

in the request window it should look like this:

javascript call
External procedure/myReport

quote:

The first button would be attached to run the focexec. You would then hide this button on the page.

The second button would be used to run your validation function. Your validation function, when passed, would then fire the click event on the first button.

This is the only way that I know to do your own validation at this time.

That's a lot of fiddling in this great new world of App Studio 48.1.04...

OK, I don't know if these are the prescribed steps -- and maybe there's a shorter way -- but here's what I did, prompted by mrguru's suggestion:

1. Removed the click event for my Run button, renaming the btnRun_onclick function to btnRun_validate.

2. Changed all the return's in the validate code to return(2).

3. Removed the OnExecute(ctrl) as the last statement in btnRun_validate.

4. Added the javascript call to btnRun_validate ahead of the External procedure call in the Requests/Actions box in Tasks & Animations.

It now works! Did not appear to need a return(0) as the last statement in the btnRun_validate function, but I went ahead and put it in there...

Craig

Agree with you, Francis! Seems like a reversal in productivity to me. Is it coincidental that going from Windows 7 to Windows 8 felt the same? Will we be returning to "normal" with WebFOCUS 10??

Craig