I became frustrated that the AppActivate method of the Windows Script Host, as well as a similar method of the .NET Framework, do not activate a window. They worked with older versions of Windows, but Windows XP and above do not permit an external process to activate a window. There is one exception: the external process has to attach itself to the thread of the program whose window is to be activated. I did extensive web searching, but could not find a free, canned routine to do this. I was then able to write one using PowerBASIC. The result is a small command-line utility called ForceWin.exe (because it forces a window to be activated). The source code is also included in ForceWin.bas. These get installed in the Homer subfolder if the HomerKit installer is used: http://EmpowermentZone.com/kitsetup.exe Someone wanting to use the utility (or others included in the package) but not wanting to install everything can do a selective, manual install from the zip archive: http://EmpowermentZone.com/kitsetup.zip ForceWin.exe takes a single parameter on the command line: the numeric handle of the window to be activated. So, a JAWS script can obtain the window handle of interest with one of its FindWindow or other functions, then pass it on the command line via the Run function or the ShellRun function of HomerKit. Hope this is helpful. Jamal __________ View the list's information and change your settings at //www.freelists.org/list/jawsscripts