In cases like this, I would go with one form with a pageframe. You could configure the pageframe to be tabless, in which case, it would look to the user that they were going to a separate form but in reality they never leave the form.

IMO, it would make sequencing easier. Also, all the configuration tables could exist in one dataenvironment.

Just a thought.

>Hi Larry,
>
>Thanks for the info in this case the forms are all modeless. This is a setup routine that the user can continue setting up or not...
>
>Thanks
>
>>>Thanks,
>>>
>>>I just didn't know if there were any problems with that...
>>>
>>>
>>>>>I want to close a form and then start a different form from the save button on the first form. What is the best way to do this?
>>>>
>>>>You could just do
>>>>
>>>>thisform.release()
>>>>do form NewForm
>>
>>If the new form is modal there are major problems with it. The modality will stop program execution after having released the form. However, because you are in the Click event of a commandbutton on the released form, it isn't really released. This could generate a C5 error.
>>
>>If the form is non-modal (modeless) then you should be okay.