I agree with you and that is why i titled this thread "list of bug/issues", most of the time we can call most of the bug an issue just because it does not work as expected but it may not be a bug.

Here is a simple example of behavior change from VFP7 to VFP8:

If you have a label with a caption with only a "=" in it this will work fine in VFP7 and lower but it will throw a sintax error in VFP8 when you run the form and is not catched by a try-catch or even the error method. It will also throw the error when you open the form in design mode.

This is not a bug, it's part of a new VFP8 feature allowing expression evaluation at runtime for captions.

What i am saying is: We should have a list of things to watch for when upgrading from VFP7 and lower to VFP8. This will make upgrading much easier since after reading the list you know what to watch for in your existing code.

Stephane

>Many of the things we call bugs, MS may consider 'features.' We have to be a little more political. What I am reading here is that we mostly don't mind the unexpected results we sometimes get, that some may call bugs, what we would like however is to have a list of those ambiguous features and also know work-arounds or best practices. SO maybe we need a 'Best Practice' topic in order to be politically correct.
>
>My first submission is that we could really use the ability to expand collections in VFP8 in the debugger. This really is more of a desired feature than anything else.
>
>Currently we work around this by subclassing the collection class and adding a method that iterates the collection and throws it into the array. This is used when we are debugging and will be turned off in production.