Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Concurrency violation?
Message
 
À
16/04/2004 15:42:14
Information générale
Forum:
ASP.NET
Catégorie:
Autre
Divers
Thread ID:
00895348
Message ID:
00895709
Vues:
11
Bonnie,
So, if I understand you correctly....
Maybe I should do something like this? ...is this what you mean?
oledbCMD = New OleDbCommand("UPDATE Contacts SET " & _
                                    "Company= strMyCompany, " & _
                                    "Contact= strMyContact, " & _
                                    "Last_Results= strMyLast_Result " & _
                              "WHERE Unique_ID = intMyUnique_ID", oledbConn)
How would this affect the DataAdapter.Update()
My understanding is that it checks all the records/rows of the dataset to see if any have changed or been deleted or created. Then it calls the Update/Insert/Delete accordingly.

I'm currently only processing only one record/row at a time so that's probably not a factor today... but Monday's coming and who knows...

>Rick,
>
>I was just reviewing your original post and was about to reply when I saw that you solved your own problem.
>
>Yes, if you think about it, in this scenario anyway, it *does* matter in which order you add your parameters. How would it have any way of knowing that the first ? referred to the 3rd parameter? It wouldn't know. I've not run into this situation for because I do all my database access through StoredProcs with named parameters, so it doesn't matter in which order I put the parameters.
>
>So, I'm glad you figured it out!!!
>
>~~Bonnie
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform