S
sienayr
Greetings,
I have read and read and read posts on how to bind a form directly to
an ADO recordset and other similar topics, but what I'm looking for is
a discussion on which is the more efficient method, from a
speed/response standpoint, to supply data to a form:
1. leaving the form unbound, creating an SQL statement string and
setting the form's Recordsource Property to the SQL statement
-or-
2. leaving the form unbound, then creating an ADO recordset in code by
passing an SQL statement to the server, and binding the form to the
resulting recordset
-or-
3. same as above, but using a stored procedure with parameters and
supplying the parameters in code to create the ADO recordset, rather
than passing the entire SQL statement to create the ADO recordset
-or
4. binding the form to a stored procedure on the server, and if needed
supplying parameters to the stored proc using the form's Input
Parameters property
Does anyone know which method is more efficient, strictly from a
speed/response standpoint (don't care if one takes more code than the
other)?
Is one method better than the other for updateable vs read-only forms?
Does the amount of data being returned have any affect on which method
might be better?
I know how to do all of those options, just not sure which one is the
best way to go for the quickest response time.
The assumption in all three scenarios is that there are run-time
parameters for the query, and the file is an Access Project.
If there is a discussion on this I apologize, please point me in the
direction of the post, otherwise I appreciate any thoughts, comments,
opinions, etc.
Thank You
Ryan
I have read and read and read posts on how to bind a form directly to
an ADO recordset and other similar topics, but what I'm looking for is
a discussion on which is the more efficient method, from a
speed/response standpoint, to supply data to a form:
1. leaving the form unbound, creating an SQL statement string and
setting the form's Recordsource Property to the SQL statement
-or-
2. leaving the form unbound, then creating an ADO recordset in code by
passing an SQL statement to the server, and binding the form to the
resulting recordset
-or-
3. same as above, but using a stored procedure with parameters and
supplying the parameters in code to create the ADO recordset, rather
than passing the entire SQL statement to create the ADO recordset
-or
4. binding the form to a stored procedure on the server, and if needed
supplying parameters to the stored proc using the form's Input
Parameters property
Does anyone know which method is more efficient, strictly from a
speed/response standpoint (don't care if one takes more code than the
other)?
Is one method better than the other for updateable vs read-only forms?
Does the amount of data being returned have any affect on which method
might be better?
I know how to do all of those options, just not sure which one is the
best way to go for the quickest response time.
The assumption in all three scenarios is that there are run-time
parameters for the query, and the file is an Access Project.
If there is a discussion on this I apologize, please point me in the
direction of the post, otherwise I appreciate any thoughts, comments,
opinions, etc.
Thank You
Ryan