Hi Sergey,

The reasons:

1. My controls classes (txt, chk, etc) contain similar if not same codes that are used at the time of data-entry. This is code: repeated <g>

2. Max use of these classes will be for data-entry screens. Similar controls are required infrequently on other than data-entry forms.

3. AFAIK, if I subclass, I will have to sub classes the controls for first usage with infrequent forms. Then re-subclass them and add data-entry related codes and use in data-entry form. This IMO is adding an unnecesary level of subclassing for frequently used controls. Then again a lot of code is repeated between controls.

Please advise.

>Wwhat's your goal? Why do you need that class? What it suppouse to do?
>
>>Hi all
>>
>>This is what I have in mind.
>>
>>1. Create a Custom class as the go between. Contains all the abstract methods that will be used by the calling control (txt, cbo, chk, etc)
>>
>>2. Sub class this class for Data-Entry form and otherwise forms.
>>
>>3. Put it on the base form class. Populate basic methods
>>
>>4. Open Data-Entry form and populate subclass with method codes.
>>
>>Please advise am I on the right tracks.