Hi Nesimi,

How about just sending the plain XML back and forth ... have your middle tier do a DataSet.GetXML() to return an XML string. Have your front end send back only the changed records (again, in an XML string ... CursorToXML()). You'd have to "roll your own" update stuff in your middle tier this way (I know, Rick doesn't agree with me here <g> ... there's also a discussion on the .NET forum here), but I say this because it seems like the UpdateGram and DiffGram don't work quite right.


~~Bonnie


>Hi. Yes we are running VFP7 with SP1. I ll try to explain in steps of a typical scenario:
>
>1. FoxPro client requests a dataset from middle tier.
> As a preliminary solution, we converted the dataset to ordinary xml
> instead of returning it as it is(Because FoxPro sees the DataSet as a DOM
> document). Then used XMLtoCursor.
>2. FoxPro client does some updates on the converted cursor.
>3. then sends the changes with added, updated and deleted rows back to middle tier. (Here some mechanism like xmlupdategram/diffgram needed.)
>4. Middle tier merges the changes with its own dataset and does DB update.
>(However only diffgrams(which has different format than xmlupdategrams produced by FoxPro) can be merged into the dataset)
>5. FoxPro client gets the new data back to refresh its own cursors.
> (?)
>
>Thanks
>
>>I haven't tried this recently but make sure you're running VFP7 SP1, which synched up the XML formats better than pre-SP1.
>>
>>What are you trying to do exactly? Provide offline datasets and the udpdate the data back into the dataset?