Hello,I am a newbie to winbatch. And iam trying to debug a winbatch program. This program was written to work with WRQ Reflection for IBM to get the OLEServerName. We are upgrading the WRQ Reflection for IBM to Attachmate Reflection 2014 and the winbatch program doesnt work.

Your problems have more to do with Reflection than WinBatch. You will need to look at the COM Automation documentation from Attachmate to determine what you should be using as the progid parameter to your ObjectAccess function. Attachmate makes it available here:

The ObjectAccess function has been superseded by the ObjectGet and ObjectCreate functions. If you have a new enough version of WinBatch use them instead because it make it easier to translate VBS/VBA examples into WinBatch. Also if your version is new enough, you will also have the WIL TypeViewer that allows you to peruse installed COM Automation object on your computer. Check your Consolidated WIL Help file for more information.

Also note that the security issue was (surprise surprise) UAC related as the topic suggests. Basically, the script has to run at the same security level as the currently running object it's trying to access.

Logged

"Success is a lousy teacher. It seduces smart people into thinking they can't lose." - Bill Gates