Ongoing Performance Issue

[Guest]

I have a number of reports that use a crosstab query for the record source.
I modify the reports each week to include the new data.

Whenever I open one of these reports, whose record source is a crosstab, in
design mode and attempt to add and move fields everything everything slows
down. I click on a field to select it and wait 10 seconds for it to become
selected. Click on a field to move it and wait.

This only happens on reports with crosstab record sources, there are no
unusual graphics on them.

Anyone offer an idea??

Thank you

 

[Tony Toews [MVP]]

I have a number of reports that use a crosstab query for the record source.
I modify the reports each week to include the new data.

Whenever I open one of these reports, whose record source is a crosstab, in
design mode and attempt to add and move fields everything everything slows
down. I click on a field to select it and wait 10 seconds for it to become
selected. Click on a field to move it and wait.

Is the database split? Is the backend on a file server? If so try
opening a table and leaving it open minimized while you try this. If
this helps then see the Access Performance FAQ page at
http://www.granite.ab.ca/access/performancefaq.htm

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

 

[punjab_tom]

just use Access Data Projects; these dipshits don't know what they are
doing; or else they would have given themselves a promotion and been
developing in SQL Server

long term SQL Server is better, easier, faster

MDB is a bunch of crappy workarounds.. I mean-- listen to this _CRAP_

 

[Guest]

Name Autocorrect is always off

 

[Guest]

The database is split on several applications, but I also experience the
problem on those that are not split. The problem is consitant, only on those
reports whose record source is a crosstab query, I am not finding a solution
on your performance FAQ yet, but it is a great resource. Thank you

 

[punjab_tom]

splitting is a waste of time

learn SQL Server and just use Access Data Projects; it is 100 times
easier, faster, bigger, better, stronger

 

[Tony Toews [MVP]]

The database is split on several applications, but I also experience the
problem on those that are not split. The problem is consitant, only on those
reports whose record source is a crosstab query, I am not finding a solution
on your performance FAQ yet, but it is a great resource.

Interesting. I haven't heard of a performance problem before on a
cross tab query. But then cross tab queries aren't all that common
either.

I imagine the reason I've never come across that problem is I always
work with the FE and BE on my own system and copy the FE MDB across as
required.

I have no idea why the cross tab query would have such poor
performance on a network.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

 

[punjab_tom]

crosstab queries were the only feature in Access MDB that I could not
live without.

Once i saw 'Analysis Services' I realized how obsolete MDB is... it's
ridiculous to use MDB for anything.
especially now that SQL 2005 supports the PIVOT keyword; you can do it
natively in SQL 2005; instead of needing to use (Multi-Dimensional)
Analysis Services