>>There must be some correct (or at least acceptable and proven) ways to handle these dependencies between the main foxpro form, the environment and occurrances of subsequent forms. I feel like this is Visual 101, but I've done some cool and professional things with the app overall, but now that it's time to deliver I'm having problems with this stuff. As always, thanks for your help!
>>
>>Regards, Renoir

Ok, I've worked out some of the issues (thanks to both of you), but I still have a problem with trying to use a form to accept confirm-type input. The order of my forms (for this example) are Main (top-level and called from the Main program with a READ EVENTS), Edit (called within a button on Main with no READ EVENTS), and Evaluation (called within a button on Edit with no READ EVENTS). When I try to call a confirm form from the INIT of the Evaluation form (it is used to determine whether the user wishes to add a new record if none exists) it will either display in the Main form (behind the others), or in the Edit form (still behind the Evaluation form). I'm obviously not putting things, or calling them, where they should be. What I want is for the customer to click on the Evaluation button on the Edit form and have the Confirm form popup to ask what they want to do if there are no evaluation records. Depending on their response I either want to add a new record and display the Evaluation form or simply return to the Edit form. This seems to be much more difficult to do than I had hoped. I tried to use a simple WAIT window, but it blacks-out the screen when it appears and looks extremely clunky. Can you (or anyone out there) give me a primer on how these form interdependencies work and what I need to do to make them behave the way I need them to? Thanks!!

Please, anyone jump right in on this...multiple answers appreciated!

Regards, Renoir