>>Imagine for a moment you had the following:
>>
>>A set of classes that encapsulates operations you will need to perform against a SQL-Server Database including:
>>
>>Inserts
>>Updates
>>Deletes
>>Queries
>>
>>Further, these classes also manage the parent/child relationships that can exist. Take this example:
>>
>>You want to add an order and lineitems in one operation? How do you manage obtaining the order key from the server to pass to the children. What about transaction processing. These classes manage all of that.
>>
>>Here is the kicker. No remote views. No DBC. And yet, in the VFP environment, VFP cursors are still created, maintaining compatibility with existing applications...
>>
>>Oh wait, there is more....
>>
>>What if you could wrap business logic into instances of the data class? Wrapping business logic with data, sounds like business objects to me....
>>
>>I have worked extensively with these tools on 3 projects. To say these tools save 4-6 weeks of development time would not be an overstatement. Most importantly, the applications based on this mode of data management are far easier to support and maintain.
>>
>>
>>Have I peaked your curiosity????
>
>You've certainly peaked mine. I've been designing some objects that do some of what you say, but you are taking things to a whole new level.

Let me guess VFE next release??