Hi!

I do not know a simple sample, though I think it would not be much different from the older VFP samples. You have to use 2 CursorAdapter objects for 2 joined tables.

"tables" property here is for case you have a view with query based on 2 or more tables, and want to update both in the same view by a single update command. This is ok only for 1 - to - 1 relationship between records in 2 tables. For 1 - to - many relationship you should have 2 record sources, and thus 2 CursorAdapters.

Yes, base both remote data sources on the same connection to organize transaction for updating both tables at the same time.

>Thank you for your quick answer.
>
>To do a master detail update you would need two CursorAdapter Objects in the same form sharing the same connection, or one CursorAdapter Object representing the joined tables and putting .tables = 'table1, table2] ?
>
>I would appreciate if you'd point me to a simple sample on how to do this
>
>Thank You
>
>>Hi!
>>
>>See notes below...
>>
>>>For those having the VFP 8.0 beta:
>>>
>>>- What is the meaning of the property: .tables of the class
>>
>>It represents option "Tables" of cursor (see help for CursorSetProp()/CursorGetProp() functions)
>>
>>>- How can we implement master details forms (for remote data) like invoices in the same form using the CursorAdapter Class
>>
>>The same way as in VFP7. CursorAdapter does not give any new features but better OOP interface to PEMs of cursor (CursorSetProp()/CursorGetProp() and updating methods). Plus it generalizes work with different kinds of record sources.
>>
>>>- Generally how can I implement transactions involving several remote tables using CursorAdapter in the same form?
>>>
>>
>>The same answer. As about common transaction for different record sources, VFP8 have improved a couple of things related to organizing of shared connection, so you can have all remote sources based on the same connection, and thus use a single transaction to update all of them.
>>
>>>Dimitris