>>Should Modal forms always use Private DataSessions?

>Lincoln,
>To expand on Josh' and Arnon's statements: Assume you call a modal form from a form with a private datasession. If the modal form's datasession is DEFAULT, it will show the calling form's data session. If the modal form's datasession is PRIVATE it will have its own separate datasession.

Does it have to be called from a form? Can't I call it from a .prg, for example as an initial logon screen that checks for user_id and password and initializes an auditing/log file? Would this be an appropriate use?


>If a modal form's datasession is set to DEFAULT it will only show the original default datasession if it is NOT called from a form with a private datasession.

So if called from a form it uses the datasession of the calling form?

>This is a very useful technique to use when you want to pop up a form to edit a memo field. I've used it for fields that are rarely used/edited. Putting them on a separate form saves the overhead of loading them every time the basic form is loaded, and saves the development time of putting them into a class and instanciating them when needed.

I'm not sure I understand this. Are you saying I should not use the "DefineWindow/OpenWindow" process/property for a TexBox to edit a memo field but should creat a modal form(using default datasession)instead?

Thanks for your help.

--lincoln