I had a really strange issue with execution control alerts.
The short story is: Including JavaScript script libraries onto the form doesn’t cause problems, but including JavaScript script libraries into the JS Header suddenly causes signature issues and the Notes client starts popping up “No Signature” execution control alerts even for NotesItem.value, @DbLookup, and @GetProfileField calls that have nothing to do with JavaScript.
Very odd indeed.
Subject: Thanks - it solved our ECL-no signature riddle
We were having fits when our application starting causing Execution Control List errors. The errors were all related to one form, and there were many ECL errors. Many commonly used @functions and LotusScript functions were now generating ECL errors because there was “no signature”, even though all the design documents in the database had been signed.
After reading the post at the top of this thread, we checked for a JavaScript script library in the JS Header of the form. It turned out, we had one. We removed it (since it actually wasn’t even being used) and the ECL errors stopped. We have used JS script libraries in pages without any problems. Until now, we were unaware of any issues involving the use of JS script libraries in forms. I am curious if anyone else has seen this problem.
For the record, this problem was encountered on Notes 6.5.2 on Windows 200 Professional.