For me, the best approach would be to put the form into "Edit/Append" mode and disable/enable other controls as needed. You could create a form-level property that held the mode and add code to the form control's Refresh methods to check this property and determione what to do (e.g. enable itself).

Launching a new form is a time and resource consuming event that doesn't need to happen (IMO).

>I've created a form that uses a view in the D.E. made up of 3 tables: inventory, customers, and transactn. On the form is a dropdown linked to a field in the view called Stocknum, which is the primary from the inventory table.
>
>In the interactivechange event of the dropdown is a procedure that finds the record in the view with the value selected in the dropdown. The appropriate data from that record is then output to other objects on the form.
>
>I want to add edit and append buttons to this form.
>
>My question is:
>
>For the Edit, is it better to close the form and open a new one with that record, or lock the dropdown and unlock the other objects? Why? (I would prefer the latter for convienence)
>
>
>Thanks
>JD