Hoi peter,

>>With this notation you´re combining the logical function of the class to the technical implementation which is just plain stupid if you´d ask me.

>This problem is omnipresent in vfp. For example, a field named cLastName, where c indicates it's of type Character. Or, lcLastName, where l and c are only technical details and LastName is the function description.

This also is a reason not to use type prefixes in fields (I don't use them), nor do I see that implemented in any other database platform. However, I admit that you don't change fieldtypes just like that.

>You need a new/other language/IDE if you want to do something about this problem. In that IDE you define a field, variable, class in terms of properties. One of the properties is 'Function description'. Another prop is 'Datatype', yet another one is 'Scope', etcetera. And there is only one place where it can be changed.

>Moreover, in that IDE you can switch between views. In one view you only see the descriptors, in another view you also see the technical details like datatype and scope. How about that. Shall we start writing that IDE?

Not sure what you're trying to say and how valuable this would be.

Walter,