Walter,

>I know... yes you can do that, but in fact because of encapsulation issues you don't want to do this either, so basicly I endend up putting the same object into different subclasses of baseclasses. In fact in order to solve this problem VFP should support multiple inheritance in which all the major behaviour is inherited from the baseclass, but some methods and properties could be inherited from a custom class.

No VFP should not allow multiple inheritance of implementation. It's a bad thing. There's a significant reason that new O-O languages (Java, C#) are not allowing it.

VFP, could benefit from multiple inheritance of interface like Java.

>I guess you can. My problem with this strategy is that the contols become less independent (self contained). I want to avoid (as much as possible) on one object depending on another, esspecially for basic UI classes.

Is it really any less self contained compared to the delegation off to a UDF? I don't think so.

>OK, that is you vision. Personally I like to develop database apps like they were just applications like outlook or excell. Just see the application as a document holder. Therefore toolbars are neccesary. For example: if my reports (Crystal Reports) were generated they show in a new window like a document: You can search through the document, Adjust the view (zoom), have a document view (the group tree), can archive, print, export and mail it.

But those are basically menu replacement type toolbars. Toolbars are one click items that do the work of several menu or dialog box selections.

>About the line too long: It seems I confused it with another error which occurs when the contents of a string does not fit into the SAY borders. I forgot the errorno. This is pretty harmless error. If you look at the list of error messages there are a number of errors you typically want to ignore (but do want to log) and hide for the user.

Ok, truly nonfatal errors like that are easily trapped and logged and ignored in the Error() method.