Fabio,

>It it not rare that you think.

Yes it is. I've been using VFP since before the public release of VFP3 and used FPW2.x before that so I have a pretty long history with this tool.

>Recent remember example:
>VFPT change SEEK(),LOOKUP(),INDEXSEEK() behaviour
>( SET KEY respect on not active index search)
>on VFP7SP1 and VFP8.

Just because you ran into this specifically documented behavior change, doesn't mean that change is rampant in the product. Microsoft strives to keep from breaking existing code. This particular change in behavior I believe was to fix a bug that you'd come to rely on.

>For me, any change on Data Engine is more breaking respect to change a property behaviour.

Well we all have our priorities, the data engine is important to you, object behavior is important to others.

>>Can you give me an example of what you are talking about? ? type( sys(1) ) prints out N for me.

>? TYPE('_SCREEN.Resize()') && <-- this not eval

? type( _screen.Resize() ) && is evaluated, the context of the quotes is quite significant.

>On my test ( PENTIUM4 2.4GHz ), ERROR trapping time is long.

TRY/CATCH is expensive I never said it wasn't. I showed you one way of dealing with how long it takes to run if you had to call it lots of times.