Thanks Roi but I have to add/edit/delete multiple records simultaneously with text boxes etc. I'm using the default data session and I need to see all uncommitted changes back into a single table for another commit mechanism to work nicely.
I think my answer is going to be to use the getnextmodified() and getfldstate() functions to move changes from one alias to another and then table-revert the aliases.


>Hi David,
>
>I think you can do what you want by making the modal editing forms data session 'default'. The editing form will then use the calling forms data session, making the address.dbf available for editing.
>
>See: Forms & Form designer Re: Private Data Sessions -- What are they good for Thread #300134 Message #300903 for some additional info on the subject.
>
>Jim Booth helped out with similar situation I had. Works great.
>
>hth
>
>>I have an Address.dbf
>>In a form it is accessed to display two addresses for a single name record, say delivery and invoice address.
>>
>>I have an address editing button on this form which calls up a modal editing screen to allow the editing of two address records at once (by using separate aliases of the address table, say Adr1 and Adr2)
>>
>>Now, here's the hard bit.
>>I would like the changes made to the Adr1 and Adr2 table (add, edit, delete) to flow back into the original buffered Address table without being actually committed!
>>
>>Can I do that somehow?