Updating SQL tables using ADO

[James Koontz]

What is the best practice for updating a SQL Server 7.0 tables. I want to
do this using ADO objects and doing a batch update in a VB6 environment.
My current company passes parameters into stored procedures to update the
tables using VB 6. The dba claims this saves time by only having to give
the users access to the stored procedures. I have middle-tier objects for
the data access.

[Bill Vaughn]

I'm on their side--use SPs. It's easy to call SPs and for a litany of other
reasons it makes abundant sense.

bv

"James Koontz" <james.koontz@mail.state.ky.us> wrote:
>
>What is the best practice for updating a SQL Server 7.0 tables. I want to
>do this using ADO objects and doing a batch update in a VB6 environment.
>My current company passes parameters into stored procedures to update the
>tables using VB 6. The dba claims this saves time by only having to give
>the users access to the stored procedures. I have middle-tier objects for
>the data access.

[James Koontz]

"Bill Vaughn" <billva@microsoft.com> wrote:
>
>I'm on their side--use SPs. It's easy to call SPs and for a litany of other
>reasons it makes abundant sense.
>
>bv
>
>"James Koontz" <james.koontz@mail.state.ky.us> wrote:
>>
>>What is the best practice for updating a SQL Server 7.0 tables. I want
to
>>do this using ADO objects and doing a batch update in a VB6 environment.
>>My current company passes parameters into stored procedures to update the
>>tables using VB 6. The dba claims this saves time by only having to give
>>the users access to the stored procedures. I have middle-tier objects
for
>>the data access.
>
I am using a disconnected recordset in the user interface that contains the
information to be updated , currently all I would have to do is set the active
connection and perform a batch update and this will update the tables. Their
way, I have to create parameters using the fields collection of the recordset.
It just seems like an extra step to go through. I do value your opinion
on this though.