Figure 1. Persist DataSets Plus Pending and Failed Updates
This diagram illustrates how the OCETestClient.xsn solution processes local Products XML DataSet files for display only and the Customers file for display and updating. Saving pending customer data updates to a DiffGram.xml file and persisting failed edits to the dsEdits.xml file gives users the ability to restart a session when connected, submit changes to the database, and retry updates that caused concurrency conflicts.