Walter,
>
>>> It would be nice if there was a 3rd DataSession type which would allow the DATA to be private but not override the SET commands. Am I just being picky?
>>
>>That would be nice, but it's so simple to solve (put SET commands in your app-level base form class to be inherited by all your forms), VFP's limited development resources belong on more important issues.
>
>You're right it's easy to solve, but sometimes when things go wrong hard to tackle the problem. This also applies to the other set commands scoped to the current datasession like SET DELETE, SET TALK, SET SAFETY etc
>
>About the limited VFP development resources: I don't think it's much of a effort to enhance these settings so that we can say:
>
>SET DELETE ON DEFAULT
>SET TALK ON DEFAULT
>SET DATE TO ITALIAN DEFAULT
>
>So each new datasession inherits this DEFAULT setting. I think this would be a major enhancement which probably eliminate many questions here on the UT regarding scoped settings

I agree, that it would be nice. How will it correspond with config.fpw settings? If, for example, it would be enough to set them in config.fpw, in this case, each client may easily has his/her own settings...