Hi Rick, my bad for not understanding you wanted to use this object, which Ron has answered already. I somehow remember the question being about a VBScript book which had examples of VBScript commands which made use of wScript. methods such as wScript.echo or wScript.connectEvent. (or maybe that was someone else) I meant to say, no, you can't use those kinds of commands in a window-eyes VBScript app (so not all VBScript books are entirely applicable), but window-eyes has given you equivalents to all of these methods which are used in the VBScript books which rely on this object from Windows Scripting Host.
So, obviously, no shared objects are involved here. Chip _____ From: RicksPlace [mailto:[email protected]] Sent: Friday, May 13, 2011 7:18 AM To: [email protected] Subject: SharedObject Question HI: I understood that we could not use WScript in a WindowEyes App. I find it used in the GWToolKit and Jamal's HomerSharedObjects VBS apps that run under WindowEyes as, apparently, do standard Apps except for Registration - whatever that does. Does Registration allow the SharedObject to run shell methods? Here is one of the statements in HomerSharedObjects. Set oShell =CreateObject("Wscript.Shell") I understood this statement would not run in a WE App but it does in a SharedObject running App. My questions: How does a SharedObject running under WE allow the WScript and shell to run? Is there a document on how to create a SharedObject and Register it? Does the SharedObject have to be running, loaded into WE, or is there a way not to have to load it and have it running all the time but associated with another App? I might elect to use the HomerSharedObject since it has such a wide feature set but I don't want to step on anyone's code if I need to modify something. Rick USA
