He's referring to the Inprise/Borland approach to data started with Delphi 1.0. The tables are objects, fully supporting OOP. You can subclass your own table objects, etc., etc. Basically, everything you're used to with VFP forms as far as OOP apply to tables in the Borland products. IMHO, it's actually quite powerful, and because of that level of abstraction, it's the reason why you find more third-party database engines that replace the Borland Database Engine (BDE).

Basically, will the next version offer true table objects out of the box?

>Marcel,
>
>Are you telling us something or asking?
>
>Did your message get cut off before you finished?
>
>What is this all about?????
>
>Jim N
>
>>No more workareas, Set Database or Create Session. No more ambiguous data management.
>>No more housekeeping (close data, etc.) The objects manage the data they represent.
>>Encapsulated Data.
>>Sharing data among forms is much easier.
>>Almost complete control over if, and under what conditions, data gets written to disk.
>>Flush is now granular, right down to the rowset level.
>>Programmatic control over login.
>>Rowset-level events that fire for appends, edits, changes, abandons and deletes.
>>Field-level events that fire before datalink and after changes.
>>Explicit control over the datalink itself.
>>Finally! - the ability to freeze or refresh datalinked controls at will.
>>Morphing.
>>Filter Mode
>>Scalability.
>>Business rules move away from the User-Interface.
>>Field level custom methods.
>>Data-level validation.
>>"Live" calculated fields.
>>Heterogeneous data access (multiple data engines simultaneously)
>>and most important of all:
>>Object data - with all its benefits of reusability and inheritance.