I have an odd issue. I'm adding some custom script on top of the latest Flex/Flash scripts to get a flex application to do some special stuff in IE. My flex app essentially displays a "document". It has a navigation area which allows the user to change to another "document". I wrote some scripts to sense that change and when that happens I want jaws to say the new document. Here's the odd part. I have the window handle to the flash window within IE. If I do something like the following, MoveToWindow(hwnd) JawsPageUp() JawsHome() SayAll() Or just SayWindow(hwnd) It does two things I can't explain. First, it reads the stuff from my app in "screen order" (i.e., top to bottom, left to right), not in the MSAA order I see the stuff in the MS Accessibility Explorer. Also, and this is worse, it's saying a garbled mess of stuff from all the documents I loaded since then mix in with the current one. It's as if it's buffering stuff based on screen location and it's not ever getting rid of it. I used the AccEvent program to check that things were getting destroyed and it seems they are, but for some reason, Jaws wants to read them. If, however, I use this code JawsTopOfFile() SayAll() Then jaws reads everything as expected (no old document info). However, it says the entire IE window contents which I don't really want. But the order is fine. Is there something I'm doing wrong? I'm a seasoned experienced programmer, but I'm new to Jaws scripts so any technical information or background would be greatly appreciated. So far, I read both the basic scripting manual and most of the FSDN manual, and to be honest, I'm learning the most by reading through the scripts that were delivered with jaws. If anyone knows any other places to get good technical info, that would be great. Thanks, Mark __________ Visit and contribute to The JAWS Script Repository http://jawsscripts.com View the list's information and change your settings at //www.freelists.org/list/jawsscripts