Hi Spencer!

Like Dragan suggested.

As you don't have all the environment at hand within Execscript code, you should use some globally known object like goApplication or one of it's members. May it be a form handler, may it be something else. That works.

Keep the execscript part short. You have less possibilities of debugging. For example COVERAGE will log lines of the execscript code as being part of the FXP file execscript generates and executes, which is totally correct and true. But if afterwards you read in the log with the Coverage Profiler, it does not find these FXP files, as they are temp files.

Bye, Olaf.