>I have a Browse Window -BW- activated from a toolbar for current table or view.
On the Toolbar is an exit for that Browse.
A ‘creative user’ moved the BW, activated an inactive screen, clicked the exit =Error.
I added “show window BW” at the beginning of EXIT to get rid of the invalid reference Err.

I believe a PROPER (or at least cleaner) way to handle this would be to make BW MODAL
Snippets follow -
*Startup
Define Window BW NAME 'BW' FROM 0,0 TO 34,80;
HALFHEIGHT IN SCREEN && Main Brow Wind
ACTIVATE WINDOW BW noshow
HIDE WINDOW BW
...
SHOW WINDOW BW
...
*Exit for the Browse
HIDE WINDOW 'BW'
WINDOWNAME= ALIAS()
>RELEASE WINDOW &WINDOWNAME

found this old message from you. i am having trouble in vfp5.0 with browses. when my client clicks on the form underneath the browse, the browse is destroyed. any suggestions how i can keep the browse as either modal or as an additional window that will not be destroyed when another window is activated.

i use a toplevelform. not _screen.

thanks - brenda