Wendell,
I think I'm following you now...

Are you saying that you want to have a modal form with lookup and options, from which the user makes a selection? Then, when the user leaves the form, your main form has access to the selection made?

If so, set the uRetVal property of your modal form based on the user's choice. Then, use DoForm (code is in YourFrameworkFolder/Common30/Progs/Utility.prg) to instantiate your modal form. DoForm() returns your modal form's uRetVal property value, so you can have access to the user's choice when control returns to PatientForm.

Hope that helps,
---J

>Hello Jason,
>
>Thank you for your help. I would have thanked you earlier but my wireless router was acting up so I had to replace it.
>
>I am trying to get used to using views and business objects. The second part of my question, that I didn't make clear, had to do with with using views to call lookup forms.
>
>I have a practice management product for doctors offices that uses a patient form (3 pages) that handles about 80% of all the activites the office needs. I know that the MM data environment allows me to use this form and an intialselectedalias and thereby I can delete, add, edit and so forth.
>
>What is the best way to handle calling these lookup forms so the user can select an option and return this reference to the calling form so the the patient from can be updated based on this selection. I would like the user to be able to add an item (on the fly) if the option they are looking up is not in the associated table yet.
>
>I hope this helps explain this better.
>
>Thank you in advance!
>
>Wendell