Cristobal,

Some "Set" values are reset to the defaults on Private Datasessions. "Talk" and "Date" being 2 of them.

If you look in help and see a line such as "SET DATE is scoped to the current data session", that means it is reset in every Private session.

You need to create a base form that runs a program to modify your "Sets" before it opens any tables.

Perry

>I'm using private data sessions by setting the datasession property of all my forms to 2. This allows to open two or more data entry forms and keep record pointers, tables and views unmodified between those forms.
>
>I've come to this approach because I needed to provide the user the possibility of creating new records in foreign tables without leaving the current form. By example: create a new client without leaving the invoices form.
>
>But now I have two problems:
>1. Even when I have "Set Talk Off", the forms seem to change this to "On" and the result of every instruction appears on the form.
>2. I also have "Set date dmy", but simply by running a form (even an empty one), the status of set date turns to "American"
>
>In the first case, I had to go to the data environment and put a "set talk off" sentence in the "open tables" method; it works fine and it doesn't matter to me, given the fact that i'm never supposed to work with Talk set to On.
>
>But for the second case, I don't want to try the same approach because the status of set date is something I want to have control of, and I don't want to go through all of my forms if I decide to make a change on this.
>Even more, I've started asking myself wich other features change their behavior without any notice just by using private data sessions.
>
>Are there any suggestions to solve these problems?
>Any way to use private data sessions securely?
>Or any way to open n forms simultaneously and keeping the tables environment safe?