>Thanks Jim. I gave this a try and apparently this is no longer a valid test as simply issuing the DOEVENTS (doevents() is not a command anymore) is incredibly fast. Regardless that would not solve the problem I'm having.
>
>This also causes a headache with trying to move the mouse to another screen as it forces the mouse back onto the Fox window. While that would certainly increase our performance I think I'd shoot myself if I couldn't get out of the application window to click onto other applications.
This is a long shot, but look at the SYS(3050) function to control the amount of memory Fox uses when it is either the foremost application or not.
Greg Reichert