Calling ScriptEval from another procedure

Brian Mellert

I just discovered, in V7.6, that we can call a script from one procedure (ProcA) that actually exists in a separate procedure (ProcB). I was trying this instead of using libraries.

 

A normal / wizard built call is normally along the lines of (in ProcA):

(%ScriptEval(JScript.NET,,%Procedure.Name,%MapName,"ProcB.Client.Can_Start_AML", )

Calling a remote (ProcB) function from ProcA appears to work well

(%ScriptEval(JScript.NET,,"ProcB","ProcB","ProcB.Client.Can_Start_AML", )

(I have not tried this in V9 to see if it would work there -- been busy trying to get this other application out.)

 

I see this works in V7, but is it "wise" to try this approach, or is it wiser to make the Can_Start_AML into a library used in both procedures?

Jerome_Pearce

I have replied to your post on this in our own forms. To summarise, v7 could do this 'late binding' but I am pretty sure v9 cannot.

 

Yes, I'd advise putting it in a library in all versions, unless you have a specific need and it is fully documented, otherwise it breaks the Principle of Least Astonishment in allowing a change in one procedure to affect another directly.

 

A specific need may be, for example, a common piece of code that will need to be changed often and is shred by many procedures. In that case, I'd recommend a script file in any case. Script files are no longer supported in v9, and nor is late binding, so the question becomes moot, I think.