Is your business object compiled as a separate DLL or EXE?

>I'm using VFP5.0a, build 415. I have a circumstance where the WAIT WINDOW command is not stopping in my app.
>
>The basic sequence of events:
>
>- Form A is modeless and contains a 2-page pageframe A, with another 3-page pageframe B on page 2 of pageframe A.
>
>- There is a view-based business object on page 1 of pageframe B. This bizobj has a command button. Its .Click() method calls a custom method of the bizobj.
>
>- This custom method creates a parameter object from the bizobj view using SCATTER NAME. It then calls a modal form B, which modifies some of the parameter object properties.
>
>- On return from the modal form B, the custom method loops through the parameter object properties and updates the bizobj view fields.
>
>- Still within the custom method, immediately after the loop, a WAIT WINDOW "plain text message" is issued.
>
>I would expect my app to stop at the WAIT WINDOW and wait for acknowledgement. Instead, it proceeds right through it to PageframeA.Page2.Activate(), which in turn calls a FormA.Refresh(), which eventually blows up with an 1812 error message "SQL: statement too long" on a very simple LOCATE command (!).
>
>Superficially, this pseudo multi-threaded behaviour looks like a VFP5 bug. Does anyone else have any experience like this, or any ideas (or wild-assed guesses) on how to work around it?