Quantcast
Channel: Mentor Graphics Communities: Message List
Viewing all articles
Browse latest Browse all 1329

Re: Getting error message Cannot create ActiveX component when calling CreateObject

$
0
0

You can use the following in a vbs script file to get the mglaunch path real time without regard to changes in system settings or installed releases:

 

Optionexplicit

 

run

 

sub run()

     Dim objShell, regkey, mglaunch

    

     Set objShell = CreateObject("WScript.Shell")

     regkey = "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\mglaunch.exe\"

     mglaunch = objShell.RegRead(regkey)

     mglaunch = mglaunch & " " & chr(34) & "full path to your .sln or exe file" & chr(34)

     objShell.run mglaunch

    

     set objShell = Nothing

Endsub

 

Just put the above into a .vbs file, chance the path to suit your needs, and double-click the vbs file.

 

Just saves the step of having to remember to update the mglaunch environment variable, such as when you deploy to many users, get new PCs, etc.   I use the same script to launch any executables that require mglaunch at startup.  FYI these are any that use the CreateObject syntax in starting a new instance of one of the Mentor VX tools from scratch, as opposed to hooking to an existing open session of one of the tools.  When there is an already-open session of a tool, GetObject is used instead of CreateObject, and mglaunch is not needed to invoke the automation hook.

 

No, this is not covered in the Mentor documentation, except obliquely where is says the information can be found in the registry.


Viewing all articles
Browse latest Browse all 1329

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>