Hi,

Just wondering if somebody has rules about how to design the info classes (i.e. classes that you use to access your application's persistent object. They typically access tables, update them and s.o.)

There is such a wealth of possibilities that it is sometimes hard to keep consistency in check.

What does one put in the ancestor of these classes?

Do we pass the key as parameters to each method and let the object access the table or do we set properties and let the method get them?

Do we keep the data in a scattered property and do we let other objects access them directly.

All those approaches have their advantages and they are mostly equivalent in functionality. Of course some will be more adapted to some circumstances than others, but how does one keep the consistency in all this?

Do I sound confused? Well, that's because I am :).

TIA,

Marc