Hi Paul,
I agree with you that Codebook does not adequately separate business logic and UI. The "business classes" are based on container which is a visual component that is intimately tied to the UI. I like the accompanying book's description of OO, use cases, etc. but feel that the framwork leaves much to be desired. In particular, the problems that you have noted limit the framework's adaptability and reuse potential.
As to a non-visual equivalent to the DataEnvironment, IMHO you need to consider DataSessions, Databases, Tables, Indexes, and Transaction processing (for VFP this requires a default database). Local and Remote views also seem worth a look. You might get some ideas from an Advisor article (Oct or Nov last year I think) on "Classes that make Client-Server Easier", or something like that.
Anyway, thats my two cents worth...
Ned

> After looking at the example program in the Codebook 3.0 book, I'm a little confused as to how "separate" the business class and the "User"/Interface actually are. It looks like they almost overlap quite a bit. Shouldn't your forms almost exclusively call Methods in your business objects (I wish I had Codebook in front of me...)? I'm not sure if this is even possible, given how much interaction is sometimes necessary between your forms and your "business logic".
>
> I guess I'm just looking for someone to confirm (or correct) what I'm saying/thinking.
>
>-Paul