model and dialog settings are COMPLETE 100% unrelated to each other. We
talking apples and orange.

A model form is not a dialog form. Grand canyon of difference. That is
why....

I explain the difference here:

http://www.members.shaw.ca/AlbertKallal/Dialog/Index.html

When you launch a model form via code, it NEVER did halt the call routines.
So, a model form is complete huge large diffent then that of a acDialog
form.

A dialog form is like a msgbox command, all focus remains on that dialog
(and you can't even use custom menus, or anything else). Were as model
forms...you can open more then one in succession in code...it does not halt
code. So, acdialg and model forms are HUGE MASSIVE LARGE different kinds of
forms.

A model form is used to control the flow of the users path. Thus, if you
have a customer form, and the open a invoice form, if you make them
model..the user will have to close the invoice form and traverse back the
same way they came. I would say that a fairly large portion of my forms are
model. Dialog forms also force this traversing back, but the purpose of
dialog forms is just that...it is a dialog like a msg dialog box and NOTHING
else can have the focus,a nd calling code halts. Hardly a modern user
interface in a windows environment in which users are supposed to have a
flexible UI.

You can't open a class instance of a form in dialog mode. Thus, if you need
to pass, or retrieve values from that form, a good approach is to simply set
a references back to the calling form, or better even to create a class
object in which to pass the values back.