Re: Pass-Through performance issue

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Yes, that's certainly a reasonable approach to take.

"Nano" <nomail@xxxxxxxxx> wrote in message
news:I61pi.11734$6p3.643265@xxxxxxxxxxxxxxxxxxxxxxxx
Thanks for your reaction guys! It was the confirmation I needed to
proceed with my workaround instead of solving the issue in Access
itself.

My workaround: via interop I first overwrite the SQL of the query
(including the WHERE statement I need, like:

oAccess.CurrentDb.QueryDefs(sQueryName).SQL = sStatement

), then call the report (still with the same WHERE condition, like:

oAccess.DoCmd.OpenReport(ReportName:=sReportName, View:
=Access.AcView.acViewPreview, FilterName:=sFilterName, WhereCondition:
=sWhereCondition)

). I need to store the sql statements locally (in VB) now, but with the
gain on performance (max. 3 instead of 20 seconds), it's extra
maintenance I am willing to invest.

Thanks again!

Nano


.

Relevant Pages