Recordset reuse/Rebind Controls Versus Many Recordsets/Binding once 
Author Message
 Recordset reuse/Rebind Controls Versus Many Recordsets/Binding once

I'm creating a VB desktop application with an Access DB on the backend
using ADO. I presently reuse the connection object and the recordset
object and rebinding the controls to the datasource. Is it better to
have multiple recordsets and bind the controls to the dataset once?
Or, is it better to skip the databinding all together and reuse the
recordset object and just populate the values into the controls and
update the changes back to the database on a triggered event? This app
would potentially be converted to a multi-user environment, so I have
to consider all of resources: network traffic, server processing, and
client processing. What is the most efficient method of putting the
data into the controls?

Thanks in advance for any information that you can offer to clear this
up.



Mon, 15 Aug 2005 01:58:50 GMT  
 
 [ 1 post ] 

 Relevant Pages 

1. MSFlexgrid - how to rebind to data control recordset?

2. MSFlexgrid - how to rebind to data control recordset?

3. Data designer bound controls seem to lose their binding to the recordset with Requery

4. Data designer bound controls seem to lose their binding to the recordset with Requery

5. Unable to reuse ADO.Recordset connection using VBA script in Excel

6. Problem reusing ADO.Recordset object in VBA script in Excel

7. Opening, Closing, and Reusing Recordsets

8. Unclear on Reuse of Connection & Recordset Objects

9. Finding a record in a Bound recordset (bound using the DataEnvironment)

10. Finding a record in a Bound recordset (bound using the DataEnvironment)

11. empty recordset cannot be bound to control

12. Bind an ado recordset directly to an ado data control (adodc)

 

 
Powered by phpBB® Forum Software