Access 2003 Crash (Possible Memory leak) with a Pivot Table

[Guest]

Hello,

I inherited a non-working database when I took up my current position. It
is used to show attendance data for Students so that they can be chased up
and a pivot table was used.

All parts of the database seem to work fine. You can see all the data in
the table view without any problems etc. When you go into the pivot table
view the first few records look fine. Then once you scroll down it locks up.
When you look under task manager Access is just chewing up memory and
processor time and just continues to do this.

The amount of data that the database uses is pretty small. It links to
tables which are in other databases. Once the make query is run to make the
table that the Pivot Table is created from, it seems to be around the 25Mb
mark. The computer I am running on has 2GB of memory so I don't think that
is an issue.

I have tried moving the data to a local drive, to take the network out of
the equation but that doesn't help.

Anyone got any ideas? Are pivot tables known to be a bit dodgy?

Thanks

Ian

 

[Guest]

It could just be a bad design. Possible something like a Cartesian join which
is creating millions of records.

Before I forget, don't worry too much about the CPU usage. Access looks like
it's burning up the CPU but it really isn't. If another program needs the
CPU, Access ususally hands it over readily.

Tony Toews has a web page on performance issues. Check out:
http://www.granite.ab.ca/access/performancefaq.htm

It could also be a corruption issue. Tony Toews also has an excellent web
page on database corruption.
http://www.granite.ab.ca/access/corruptmdbs.htm

Allen Brown also has excellent info on corruption.
http://allenbrowne.com/ser-47.html

I have a white paper in a Word document named Fix Corrupt Access Database
towards the bottom this page:
http://www.rogersaccesslibrary.com/OtherLibraries.asp

 

[Guest]

Thanks for the response. After talking to the user it turned out that the
pivot table view was largely irrelevant. The data was to be used in a mail
merge which she was doing largely by hand. I've sorted all that out now so
she can just print merge from Word after running the database.

Don't think I'll ever really know what was going on with that form though.
Pivot view crashes, any other vie and it was fine. Bizarre.