Using a VFP7 SP1 .exe on Win2K SP2 and IE 6.

The primary form (after a Login form is invoked/released in the MAIN program) has a line in its .Init() saying:
Application.Visible = .F.

When that line is NOT there the form terminates and I can go into the IDE, make some code revisions, then build a replacement .exe.
When that line IS THERE the form appears to terminate correctly BUT I cannot subsequently build a .exeto replace tht old one - I get a sharing violation. A look at the Task Manager process list shows that the .exe in question is still in the list! I have to end that process to be able to build a .exe replacement.

All that I have to do to get this condition is to start the .exe, get past the Login form to display the primary form, then exit that form.
Doing this WITH the line in question causes the condition and commenting that line and doing it again lets the form terminate normally/cleanly/completely.

The primary form has property ShowWindow set to 2-as Top-level form and WindowType as 0-modeless.

The primary form, in its Init(), invokes a "daughter" form using the command:
DO FORM MerchProf NAME ThisForm.ProfileFormRef LINKED
which ALSO has properties ShowWindow set to 2-as Top-level form and WindowType as 0-modeless.

Neither of these forms has AlwaysOnTop set to .T.

Buttons on the primary form will invoke other forms as MODAL forms, each of which have property ShowWindow = 1- In top-level form.
In addition, one button on the primary form as well as some buttons on one of the Modal forms may do a BROWSE...IN WINDOW .

Does anyone know what I need to set to ba able to hide the VFP main screen without experiencing this problem?

Thanks
Jim Nelson