This is really not a bug. Just look in the Help at "Commands that Scope to a Data Session".

There are a lot of SET commands that are scoped to data session. If you need multiple data sessions, you must set them again for each data session.

This may be extremly useful when you need different settings for different data sessions.

If you need the same settings for all forms/all data sessions, just put all your settings in a single App method or prg file and call it everytime from the Init() method.

Vlad

>Last few days I'm trying to make filer.scx work as expected (by an fox
>addict), and I'm glad to report I'm making progress (without filer.dll).
>Along the way I've stumbled upon a... well, M$ would say "the behaviour
>is by design", and I'd have a few words about the *$%&(**@# design.
>If a form has its own datasession, then the datasession keeps the Set
>Date, Set Century, Set Hours and maybe some other settings I've not
>stumbled upon yet. If the datasession is set to 1, it all works like a
>charm; if it's two, I get american date, 12 hour clock and century off -
>nice defaults for some, and a nuisance for others.
>
>I've found no way to clear these settings out, or to edit them - I just
>made a workaround:
>
>* Well this is an incredible bug, or at least an undocumented feature
>* (whatever) - as soon as datasession goes 2, the date gets set
>* to American (probably due to some bytes in .pjx file header)
>* and switches so as soon as form is instantiated. So I had to
>* write this kludge:
>
>set datasess to 1
>cRealSetDate=set("date")
>nHours=set("hours")
>cCent=set("cent")
>set datasess to 2
>set date (cRealSetDate)
>set hours to nHours
>if cCent="ON"
> set cent on
>endif
>
>Is there any decent way to avoid this? I'd prefer if the data
>environment would respect the defaults of the system where it's
>installed to and not where it was created first.