Hi mike,

As you´d probably know, I don´t agree with the three-character prefix, especially for bizz objects.

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.

For example if I´ve got a Bizz object based on a custom class and I decide to change that to a datasession class should I rename that class, breaking all existing code refering to that class?

I´ve got a menubutton constructed out of two icons, a caption and a container class, because VFP does not allow detailed positioning of icons in a command button. If I named this class cnt_menubutton, should I rename it to cmd_menubutton when change the implementation to a single command button in VFP 9 ?

A class should be named after its logical function and exclude anything refering to its technical implementation because the technical implementation can change...

Personally I do use a prefix for my own created classes beginning with TAX_ but it does not refer to its technical implementation or any other thing that could change over time.

My two cents...

Walter,