Mike,

>This not a very convincing arguement to a weak suggestion. There are lots of things that have multiple settings that may be defaulted to the one the you don't want. That's why they let you change it. And to simplify it is the point of your framework.

Let me ask a question... Which setting do you use the most. I'm sure the vast majority of VFP developers use the SET DELETE = OFF setting. AFAIK, most applications written within VFP have a default setting of ON. So why is the default setting to OFF ? It does not make sence to me !

About the framework. As I stated earlier, In my personal framework it's set to ON, even for private datasessions. But as soon as I step out of the framework (for whatever reason) this setting bites me once in a while.

>The reason its defaulted off, is because thats was the behaivor of Fox before SET DELETED was available. Changing it now would not be very backwards compatible and create headaches for people that want SET DELETED OFF or didn't know it existed.

As you think clearly, this is a very, very weak argument. In the early days we didn't have datasessions, and we could just put one line of SET DELETE ON in our start procedure. Now we have to set it again for each new datasession. This is clumsy and is one off the causes of bugs in our software. IMO, the large majority of developers use SET DELETE ON setting for their apps. Why should MS make it so hard to us, if it could create a much more conveniant solution.

What about new developers ?? I can remember when i used DBASE III for the first time it really searched my head of why deleted records still are their when I browsed the table. To new developers, not comming out of the xBase world, this behaviour makes No sence.

The VFP team had no difficulty at all to change the SET CENTURY setting from OFF TO ON in the move from VFP5 to VFP6. People who had it defaulted to OFF had to adapt.

AS for the people who want their SET DELETE to OFF, they have to explicitely to set it off: As I think this is certainly NOT a large number off developers, and I don't think they alway's use the OFF setting, they have to get used to it.

>I find it hard to believe that everybody needs it ON.

I never did say that everybody will in all cases, but IMO the vast majority will. For example: Most people are right handed, so most scissors are made for right handed people. Being left handed, I've got to be used to right handed scissors. I'm sure that if about 50 years most people are left handed, the most scissors would be left handed; Then the right handed people would have to adapt to the most common setting.

I can't see why this is so much different to our situation. If the most common (and usefull) setting is on, why should we make it us difficult, in favour of just a few developers who likes to set it to on ??

>One thing that would be nice, is a "Deleted" property for the Session object, along with any other of these scoped SET commands.

I certainly agree, but again this cannot be a substitude for the default setting.

Walter,