Russel, you must be referring to:
Unlike TestComplete projects, references between script files in a script extension package are not allowed. Called routines must be located in the same script file as the caller ones.
But the thing is:
There are references to *other* script extensions, which are called using the corresponding Runtime Object. I could swear that I have done this in other extensions, but I will double-check it tomorrow.
However, the Script Extension module does not complain about this, so I am assuming that failure for this reason would happen during runtime, once the execution gets to the actual point where it needs this Runtime Object, but it is instead failing before even entering the function.
In the example that I provided, which has allowed other users to replicate the failure, I deliberately commented out the use of other script extensions, since this was also one of the suspects I wanted to discard first.
I am really running out of ideas, and I have this feeling that the answer will be either something really stupid (some capital letter, some key word that I shouldn't be using, ...) or something really esoteric.
