Your network then is probably the source of most of the slowness you are experiencing.

I don't know of a single serious developer that ever directly uses a VFP Baseclass for anything but deriving their first level subclasses. These first level subclasses in my case fix what's wrong with the VFP Baseclass. Things like setting Label.AutoSize = .t. and BackStyle = transparent. Setting the checkbox.Value = .f. instead of the idiotic 0. Providing a common Error() method override so that all objects get proper error handling. Fixing the TextBox.KeyPress method so that backspace doesn't cause you to leave a field and start destroying the contents of the previous field.

From my subclasses everything else is derived. I also usually have a client classlib that puts a layer where I can make client wide changes and add the specific classes developed for the project.

>Yeah I know what you mean. But in this case I know for sure that the app I inherited did not need anything in the custom classlibs which ARE on the network BTW.
>
>I guess I'm a little fuzzy about this idea of subclassing ALL the baseclasses and using this subclass library for your objects. It seems there has been some debate as to whether this is such a great idea or not. Especially if you can always add custom classes using code. Am I missing something here?