Yes, it is..

I didn't realize that was the problem - I had to dig through the code. I downloaded and used WMIQuery pretty much as-is, and it had worked very well until this project.

So, now - what do I do? It's a moral dilemma, no?

Do I modify the function to support NoVarsInStrings? Won't that cause scripts that don't specify this to fail? Or - do I check the NoVar setting on entry to the function, turn it off, then restore it before exiting the function?

Or - creative coding:
Code:

; Get setting
$RC = SetOption('NoVarsInStrings', 'On')
; Define "$" or "$$"
$Dollar = IIf($RC = 'On', '$', '$$')
; Restore setting
$RC = SetOption('NoVarsInStrings', $RC)
; Define EXE string
$EXE = $Dollar + 'Varname'
Execute $EXE


Granted, there are only a handful of functions that utilize the Execute statement, but its something to consider as my function library grows, and I grow more dependent on it.

Whadda ya think?

Glenn
_________________________
Actually I am a Rocket Scientist! \:D