Unless you include the /codebase option in the RegAsm call, your CreateObjects only work if they're in the current working directory of the script (unless you have defined extra details in wscript.exe.config, cscript.exe.config, or machine.config).
I've also had issues confirming I have the right object name to create. In other words, ProgIdAttribute does not always seem to be processed. -- Regards, Mark Hurd, B.Sc.(Ma.)(Hons.) On 1 August 2013 15:26, Greg Keogh <[email protected]> wrote: > It's working now, but I'm not sure what I did. It's something to do with > regasm version. If I run regasm from the VS2012 command prompt then > CreateObject fails, if I run it specifically from the Framework64\v4.0.30319 > folder it works. Both regasm seem to have the same version and run correctly > but give different behaviour. > > I haven't got time to diagnose why it does and doesn't work at the moment > (who was that guy who said "everything works for me" a couple of weeks ago?) > > Greg K
