Ado child updating
If a Web application is made open to anonymous users? providing a good, if not optimal, level of scalability is a sort of survival test.Scalability is related to performance, but it can't be identified exclusively with that.Sometimes compound queries can be more effectively accomplished splitting queries; sometimes not. Data-driven applications must also format data in such a way that end-users can easily and pleasantly consume it.Submitting changes in batch mode, exploiting the Data Set and its disconnected model, often appears as the perfect solution. The serialization mechanism of the Data Set would increase that by a factor. More often than not, data is made of cross-related tables in which parent/child relationships are in place to define the data model and to extract a specific subset of information like detail views and subtotals. NET provides you with the tools to configure the runtime environment so that changes can automatically be cascaded from parent to child rows.In ADO, this object is the most important and the one used most often to manipulate data from a database.
The BDE considers any SQL join to be read-only because inserting, updating, and deleting rows in a join is ambiguous.
No error occurs, because the update has been applied successfully.
ADO, compared to the BDE, has taken a more practical approach to the problem.
For example, the Join Data example is built around an ADODataset component that uses the previous SQL join.
If you run it, you can edit one of the fields and save the changes (by moving off the record).