Disconnected Data: Help!
-
Hello world :cool: I've written an app that employs disconnected data via datasets. I had a situation lately where a user modified over 10 records (out of a total of 25 contained within my dataset). When the user tried to update the datasource with their changes some of those records violated database rules. The user then had to manually scroll thru the dataset SEQUENTIALLY to see which records caused the update to fail. How do I modify the app so that in such a situation it automatically displays the first record that causes the update to fail? If it is any help, the app was built using the Data Form Wizard in VB.NET. Rommel the iCeMAn, Computer Programmer, Barbados, West Indies.
-
Hello world :cool: I've written an app that employs disconnected data via datasets. I had a situation lately where a user modified over 10 records (out of a total of 25 contained within my dataset). When the user tried to update the datasource with their changes some of those records violated database rules. The user then had to manually scroll thru the dataset SEQUENTIALLY to see which records caused the update to fail. How do I modify the app so that in such a situation it automatically displays the first record that causes the update to fail? If it is any help, the app was built using the Data Form Wizard in VB.NET. Rommel the iCeMAn, Computer Programmer, Barbados, West Indies.
I have a suggestion that u might wanna look at, what you can do is to highlight those records that caused the problems and let user rectify. BTW : I am curious, how can u let user update fields that can cause DB error? wanna leave an example here? thx "Rejoice always, pray without ceasing, in everything give thanks; for this is the will of God in Christ Jesus for you."1Thess. 5:16-18
-
I have a suggestion that u might wanna look at, what you can do is to highlight those records that caused the problems and let user rectify. BTW : I am curious, how can u let user update fields that can cause DB error? wanna leave an example here? thx "Rejoice always, pray without ceasing, in everything give thanks; for this is the will of God in Christ Jesus for you."1Thess. 5:16-18
You're thinking along the same lines as me. However, the question is, how does one determine which records are the rogues? For example, if we are sending 5 records back to the datasource but one has caused a concurrency violation, how do we know which one has caused the violation? :confused: As for your question I think it's just a case of highlighting the field (on the data-entry form) that caused the error, allowing the user to correct the data, then allowing them to save the data again (via the appropriate command button on your form). Rommel the iCeMAn, Computer Programmer, Barbados, West Indies.