>>I am not completely sure that creating a (for example) customer object and having all use of this table done via that object as the way to go
>>is this what you are suggesting ?
>>what are the benefiets u found in your approach?
>>(I can tell you what my approach is but I guess the folks here are tierd of that :) - so if you are interested I can email u)
>>
>Hey, I am never tired of a piece of nicely written code :) If you have it, -
>I'll be checking my e-mail more often...By the way, the commented piece
>was just a christomatic example. The base classes collection should
>alter the conventional look of a table-like set of objects into your
>typical OOD'ed class library.

yes naturally, but why do u think it is better to have a seperate
non-visual class for each table rather than e.g.
having a visual class for entry-screen and use a sub-class of that with
each table (while adding the differnt fields directly as differnt widgets ) etc.

Arnon