Tore,

>Compared to for instance many changes in VFP8, I think the change I and other want, is minimal and only a good one.

I've not said that this would be a bad change. It is not a change that I need. Those that need it can add to the wishlist.

>What about the SQL change which made it necessary to include the SET ENGINEBEHAVIOR ON/OFF command?

Better ANSI compliance is a good thing, since VFP SQL allowed people to write SQL statements that would not work under the new strictness, the EngineBehavior was put in to allow the old code to still run. Like I said several times, backwards compatabily is an important thing in FoxPro.

>And the bindevent/_screen.resize/_screen hook issue where the behavior was changed in such a way that the actual example in help for VFP7 caused a C5 error in VFP8?

Well that sample turns out to cause other problems like mysterious GPFs IIRC. The new behavior is a more capable solution. I'll take a stability tradeoff over a small change that I might have to make in one class somewhere in my system.

>As far as I can remember, the issue we discuss here, is the only situation were VFP does not raise an error were the situation often, but not always, should logically raise an error. A new SET OPENDIALOG ON/OFF command and a minimal change in the not default behavior would make everone happy.

Yes, I guessing though that since Europa is so far along already, this change probably would not make it into VFP9.

>although many of the new stuff was not necessary if we follow your reasoning. With all due respect, I think your attitude is counterproductive.

Hardly so Tore. I've asked for a great many of things to be added. I really enjoy using all the new capabilities that get added with each release. I think this thread has made a bunch of noise about one tiny little thing.

And we have to code/test for this issue anyway, folks might as well do it however they see fit.