My standard idiom is saveCursor() invisibleCursor() saveCursor(): The first saveCursor keeps track of which cursor was active to begin with, and the second saves the position of the invisible cursor before I move it. On Tue, Dec 02, 2008 at 04:32:27PM -0500, Donald Marang wrote: In the examples I have seen for using the SaveCursor and RestoreCursor functions, they use the following order: InvisibleCursor () SaveCursor () perform statements that move the focus... RestoreCursor () If the save and restore functions work like a stack, wouldn't the SaveCursor function need to be called first, and then change cursors? I am a little confused here. I am finding my application being continually with the InvisibleCursor active, and I am not sure why! Don Marang __________? Visit and contribute to The JAWS Script Repository http://jawsscripts.com View the list's information and change your settings at http://www.freelists.org/list/jawsscripts -- Doug Lee, Senior Accessibility Programmer SSB BART Group - Accessibility-on-Demand mailto:doug.lee@xxxxxxxxxxxxxxxx http://www.ssbbartgroup.com "While they were saying among themselves it cannot be done, it was done." --Helen Keller __________ Visit and contribute to The JAWS Script Repository http://jawsscripts.com View the list's information and change your settings at http://www.freelists.org/list/jawsscripts