Hi!

Just a suggestion: try to set the _VFP.AutoYield to .F. before runnign that long query.

In general, modality usually breaks when some non-modal window is opened after modal. When runnign SQL Select, it might display a status window, that is probably a cause of the problem. By setting _VFP.AutoYield to .F. you will disallow any events processing during runnign of th query, so user clicks will be processed only AFTE VFP code is finished.

There are a few other samples of breaking modality, but most of them seems related to Windows Events or to Windows in general.

I hope this helps.

>Windows XP
>Visual FoxPro 7.0 SP1
>
>I run a modal form on top of a modeless form. The one on top is smaller. When it is sitting on top of the modeless form, not doing anything, if I click outside the modal form I just get the default beep. This happens no matter where I click off of the modal form.
>
>Now, on the modal form I have a button that does a SQL select against a 300,000 record table and then does some processing in the resulting cursor. Once I click on that button and the processing begins, modality seems to go out the door. If I now click outside of the modal form all screen refresh and activity on the modal form stops, the underlying modeless form title changes to Beyond Gold (not responding). All the while the processing is continuing, but no user, looking at the screen, can tell anything other then it must be locked up.
>
>Can anyone assist me in rectifying this problem.
>
>TIA
>DJ :o)