A
AG
Access 2007 front end ODBC linked SQL Server 2005 back end.
Any report with a view, table, query or passthrough query as a recordsource.
It seems that just about any design activity causes Access to query the
source.
This is in design view.
Start a new report based on anything with an ODBC source. Try to add new
controls by dragging from the field list.
Access queries the source once for each control, for each table in the
source. E.G. if a view is based on 5 tables, the full table is queried for
each control that uses it for a source.
When the tables contain a lot of records, it can take several minutes before
the controls can be added to the report. This is all with a 3.2G quad
processor maxed out.
I am monitoring this in SQL Profiler, so I am not guessing.
Once controls are added to a report, just clicking on a bound control,
causes Access to query the full table again - if the property sheet is
displayed.
So, if I just want to move or reformat or whatever a control, I need to wait
for Access to finish OR constantly close and reopen the property sheet.
The problem has nothing to do with the source (view, qurery, etc.)
efficiency. The reports perform very well at runtime.
There is similar behavior with some bound forms.
Does anyone know why this is happening or have a workaround?
Thanks,
Any report with a view, table, query or passthrough query as a recordsource.
It seems that just about any design activity causes Access to query the
source.
This is in design view.
Start a new report based on anything with an ODBC source. Try to add new
controls by dragging from the field list.
Access queries the source once for each control, for each table in the
source. E.G. if a view is based on 5 tables, the full table is queried for
each control that uses it for a source.
When the tables contain a lot of records, it can take several minutes before
the controls can be added to the report. This is all with a 3.2G quad
processor maxed out.
I am monitoring this in SQL Profiler, so I am not guessing.
Once controls are added to a report, just clicking on a bound control,
causes Access to query the full table again - if the property sheet is
displayed.
So, if I just want to move or reformat or whatever a control, I need to wait
for Access to finish OR constantly close and reopen the property sheet.
The problem has nothing to do with the source (view, qurery, etc.)
efficiency. The reports perform very well at runtime.
There is similar behavior with some bound forms.
Does anyone know why this is happening or have a workaround?
Thanks,