>Hmmm... I don't think this is the way to go. If for this reason we would require static variables, we should be consistent and also ask for multiple inheritance, (Operator) overloading etc.

Even C++ programmers don't use multiple inheritance much. Too complicated.

>I have the opinion that VFP is a very fine language because most things (aside from OOP) are straightforward, easy to understand and allow us to write maintainable code rather easy (relative to other languages, like C, C++). Having the goal to make VFP like another language could IMHO take away the strengts VFP has.

In the same direction, do you suggest that VB stay like it is and doesn't include inheritence to keep it simple?

>If we really want to do something that cannot be accomplished within VFP, it's better to use another language rahter than expand VFP to make this possible *IF* this something is some exceptional requirement that is only used in a very few limited cases.

You would let VFP down to write a database application in another langage that doesn't do well with database because this other langage as a feature that doesn't exist in VFP?

>Hereby I think of the Assign and Access methods added in VFP 6.

I do not agree with your appreciation (or lack of) of the Assign and Access methods. I find these methods very useful has it enable me to encapsulate property validation inside my class and doesn't require me to make 2 methods public to access a property, as in VB.

>I'm sure there are also other examples to find which indeed are not as neccesary than things we really need (Better menu implementation (with pictures), maybe OOP menus, Dockable IDE forms, Resizable toolbars etc, all classes maintainable within the classes tab in the project manager, recycle deleted record, revise of the RELEASE command and method, FIX of the SQL filtered resultset behaviour, etc.).

The priorities varies from one developer to another.
- Yes I would like a better menu implementation.
- I think that dockable IDE forms will be included in VFP 7.
- Resizable toolbars? We can allready resize them.
- All classes maintainable with the class tab in the project manager. I don't understand that one. Can't you use the Class browser?
- Recycle deleted records. I want that one too.
- What about the Release?
- Fix SQL filtered resultset. If it would mean slower query time, I'm against it. You allready have the NOFILTER option.

>I see a lot of people demanding for a better report writer. Since I use Crystal Reports, I think it's better to use this Report Writer to make reports. the VFP team would definitely have a very hard time to make such an advanced Reportwriter. Sure it needs some VFP Database support, and aligning objects is a real pain. But I think a lot of the VFP developers would benefit if CR was to be included with a future release of VFP.

IMHO, Crystal Reports is better than VFP report writer in certain areas, but it still sucks.