I did not create a generic data mechanism for the book. Microsoft is
working on one or two, and as you say there are commercial ones out
there.

The problem is that a very large percentage of organizations must deal
with data from multiple backend systems, and it is very difficult to
create a truly generic persistence layer that can deal with 'joins'
across multiple, disparate databases, XML files, text files and who
knows what else.

Due to this, the framework in the book leaves this open-ended. It is
very clear where the data access code goes and how it is used by the
business objects, but the actual data access code (or the use of a
generic persistence layer) is entirely up to you.

Rocky

> -----Original Message-----
> From: Chad Christians [mailto:cchristians@i...] 
> Sent: Thursday, March 13, 2003 7:49 PM
> To: expert_vb_business_objects
> Subject: [expert_vb_business_objects] Persistence
> 
> 
> Will the new archetecture still force you to write a 
> persistence class 
> for each business object class or will persistence be generic?
>