>Would you advice to use CAs like RVs? I mean, put them on any form's DataEnvironment? (That's how I generally I've been using RVs on VFP since VFP6s early days. I fell in love with Remote View buider.

I don't like dataenvironment... the code in there is not easily accessible, you have to rightclick and select from dropdown somewhere on the form itself to access its code, and then the code in the rest of the form isn't at hand. So it's more like a hidden backroom. The main reason against it is, actually, that form classes can't have it.

Which is why I prefer to create CAs in the form's .load(), or rather create the bizobjects and the bizobjects then have their own CAs. The (not so new) three-tier scheme - keep visual stuff on the form, logic in the bizobjects, and the CAs are your data layer. So my form class would have

this.biz=NewObject(this.bizClass, this.bizClasslib)

and these two properties would be set at design time - regardless of whether it's a .vcx or .scx (and I know one case of .prg forms, believe it or not). The bizobject can have its child bizobjects - there are frameworks out there which actually handle the parent-child relationships between your business objects, cascading updates, copying foreign keys when creating a child record etc etc.

I even know a guy who wrote such a framework in a couple of months (along the regular work), and it was rock solid.