odbc advise requested

[whistler]

I am populating a dao recordset in VBA code behind a form from a mssql dtabase through odbc.

This is strictly done in a single-user application. Also, there will never be a record update as long as i am in this vba code.

My question is: what are the smartest option and type settings for this in the openrecordset code, i.e. which would give the best performance ?

Thanks in advance,

Jos


--------------= Posted using GrabIt =----------------
------= Binary Usenet downloading made easy =---------
-= Get GrabIt for free from http://www.shemes.com/ =-

 

[Bob Hairgrove]

I am populating a dao recordset in VBA code behind a form from
a mssql dtabase through odbc.

This is strictly done in a single-user application. Also, there
will never be a record update as long as i am in this vba code.

How can you be sure?

My question is: what are the smartest option and type settings
for this in the openrecordset code, i.e. which would give the
best performance ?

This is very difficult to predict without knowing what your SQL
select statement looks like, whether you are querying a table or a
view, what indexes there are, whether or not you are doing one-off
SQL statements or using bound variables with prepared statements.

I would start with the defaults and test. If it is fast enough, then
just use those. Otherwise, there are lots of other potential
bottlenecks (network traffic, missing indexes, or maybe file system
problems on the server, for example).