Forum Discussion
ory_z
14 years agoContributor
Hi David,
Thanks for your suggestion.
The Exception thrown was:
An exception occurred in the "ESLScripts" unit at line 45:
Microsoft VBScript runtime error
Object required: 'GetESLCMD'An exception occurred in the "ESLScripts" unit at line 45:
Microsoft VBScript
runtime error
Object required: 'GetESLCMD'
And was due to the following line (when GetESLCMD was not returning an object):
Set ESLCMD = GetESLCMD
So effectively I was capturing a VB Script error with my exception handling.
I now understand this was due to not setting GetESLCMD to Nothing when it can't find the correct window. I have updated my scripts according to your suggestion and will keep you updated about the results.
However, I still think there is a problem with the Async call followed by a Delay, obviously my updated scripts now do not have a delay, but none the less it might be a good idea for you to look into this.
Thanks for the help.
Thanks for your suggestion.
The Exception thrown was:
An exception occurred in the "ESLScripts" unit at line 45:
Microsoft VBScript runtime error
Object required: 'GetESLCMD'An exception occurred in the "ESLScripts" unit at line 45:
Microsoft VBScript
runtime error
Object required: 'GetESLCMD'
And was due to the following line (when GetESLCMD was not returning an object):
Set ESLCMD = GetESLCMD
So effectively I was capturing a VB Script error with my exception handling.
I now understand this was due to not setting GetESLCMD to Nothing when it can't find the correct window. I have updated my scripts according to your suggestion and will keep you updated about the results.
However, I still think there is a problem with the Async call followed by a Delay, obviously my updated scripts now do not have a delay, but none the less it might be a good idea for you to look into this.
Thanks for the help.