Replacing the VBA code inside Modifier, with an Extender Enterprise script
Steve Simon, PDG Consultants
In Extender Enterprise, you create ‘Actions’ which are events on either Extender Windows or GP windows. Whether or not you can replace your VBA code with Extender code is depends on the nature of the code you are currently using.
The reason is that Extender Enterprise typically uses ‘after’ scripts for processing – so any ‘Before’ scripts you are currently using (typically for validation) likely won’t be workable in Extender Enterprise.
I’m not saying that it isn’t possible that you can’t do this – just that going to Enterprise is going to be a sure thing necessarily.
Thanks, Patrick. I’ll document the VBA code to see what it does. It may not do “Before” scripts. If it does do “Before” scripts, then perhaps I can replace it with Sanscript. Will Modifier accept Sanscript in place of VBA?
I think you mean “if it does NOT do ‘before’ scripts” as I noted that Extender typically does ‘after’ scripts. As for ‘does modifier accept sanscript’, no not really. everything starts and ends with vba in modifier. And actually, if you have a modified form – you can’t reference those fields with dexterity – you have to use vba (or vstools).
That’s a bummer. Oh well, I’ll open it up (the vba code) and see what it does. Thanks for your guidance.
If you would like to submit an answer or comment, please sign in to the eOne portal.