Possibly you look up the help SET DATASESSION Command for all SET on private datasession. I recommend to set all to that what you expect
EXCEPT
Bring your prog in line with the system / user expectation:

*read formats from OS (this is a one time read)
 SET SYSFORMATS ON							&&Standard OFF
*turn it off again, now anything is like the OS 
 SET SYSFORMATS OFF
* now stuff that might change with SYSFORMAT you like different or forced
SET CENTURY ON

Note: This might have side effects. If you run the prog on my comp now, it looks nice to me with 3,14 instead of 3.14 for pi. I would not buy otherwise.
But now stuff dealing with string to num may be odd
For example EVALUATE(TRANSFORM(PI())) must fail, EVALUATE expects dot while TRANSFORM creates comma. Keep that in mind if you distribute outside the empire.
This goes for the other settings described in SET SYSFORMATS too.

>Thanks for the input Naomi et al,
>
>I placed following code in the form Load events:
>
>SET CENTURY ON
>*SET CLASSLIB TO
>SET DELETED ON
>SET ESCAPE ON
>SET EXACT OFF
>SET EXCLUSIVE OFF
>SET MULTILOCKS ON
>SET PROCEDURE TO
>SET SAFETY OFF
>SET STATUS bar off
>SET CLOCK STATUS
>SET TALK OFF
>SET NOTIFY off
>
>The user login form has these settings in the Load eent of the login form. The login form also has a Registration button that pulls up another form (register form). It simply hides teh user login form, and brings up the registration form. When it pulls up the registration form, i notice the statements on the screen, "Selected xx records in 0.005 seconds etc".
>
>I was assuming that the Set Talk Off would have prevented that from showing.....
>
>
>>Thanks for the input. I have all my sets in a custom class (oPro.SetEnv). >Thanks. So I am using private datasessions in my forms data environment. So does that mean I need to Set Talk to Off in all Load events of my forms?
>>
>>That, and a bunch of other SETs, goes into a routine (in a .prg, not in an already existing object!*) which you'd call from the .load() of each form class which has private DS. And then you have it everywhere and forget about it, until someone asks a question like this :).
>>
>>The reason for the * there is that any object which already exists would execute its code in the DS in which it was created, so the settings it puts would apply to that datasession, not to your form's.
>
>Just add this setting into your custom class too.