Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2001-09-21 : 10:09:50
|
| BF writes "Hi, I'm currently working on a project that requires a recordset of 'objects' to be manipulated on a client PC. The user can add new objects locally and also delete original records (setting an active flag to zero to maintain historical data and references).Ideally the data should go through validation locally and at the database before being committed. I'm sure that the conventional way to do this would be to .update the recordset. I would rather employ a stored procedure if possible to permit validation and offer more control over the data but would not like to perform many network trips writing single records by looping through the objects since all the records should make it to the database.In short some objects will be new, some objects will be modified and some will be set inactive. I've seen and read about solutions using CSV or other parsing methods and wondered if this was the only way.I'm developing on VB6 SP5 and SQl Server 2000 SP1. Many thanks for your time.BF" |
|
|
|
|
|
Alternative to batch updates with stored procedures