Running queries in Access 2003

[sportsguy]

Not sure what happens.

occassionally i will run queries that have run before,
the hourglass will turn on, then turn off, and access does nothing
visible, but tack manager says its running 90% cpu. . .

any ideas on what is happening or i am doing wrong?

thanks

sportsguy

 

[llkhoutx]

Without more information, your symptom could mean a lot of different things, such as, the tables are quite large, your system has suffered severe memory leakage and need to be re-booted, or network traffic is signirficant if you are using a BE on a network peer or server.

 

[sportsguy]

the problem is specifically,

i have two queries than run fine, not overly complex, but 5-6 tables, and two of the tables are large, 100-200 MB. . . 300K - 400K rows.

the two queries run very quickly, independently.

when I run the two queries as a union query. .

everything stops. . .

memory leakage. . . mine or the computer?

mine happened earlier this week as i forgot how to log onto my work computer after two weeks vacation, but i hadn't forgotton my username or password. . . had to get the help desk to remind me how i had been logging on for the last six months. . .

how can i plug the leakage ?

Win XP,
Office 2003
Dell gx270 - 1 GB ram
11 gb of hard drive remaining. . .

thanks

sportsguy

 

[llkhoutx]

That's a huge number of rows for Access. Access starts degrading with 50,000 rows.

Multiple simple queries will run significantly faster than one huge query.

Memory leakage is a Windows problem. windows does not completely reclaim memory when a program is closed. The problem is critical with Win98 and significantly less so with XP.

Are you using a SQL Server, Oracle or other BE. If so, your problem might be network traffic/loading.

 

[MarkP3]

Try this in XP w/Dell...

I had all sorts of problems with Access 2003 and XP on Dell. Accidentally, while working with the Microsoft Access support people, this fixed it all....

Go into SAFE mode (with networking, if necessary) and install the GENERIC TEXT printer (if it will let you) and make it the default printer. Run the queries and reports. Then, go back to the normal login, reselect your normal printer and try again.

This bizarre "fix" from their engineers fixed all sorts of problems I've been seeing with Access 2003.

 

[llkhoutx]

I use Access 2003 on a networked Dell with Windows XP and a myriad of printers for more than a year. I haven't encountered any problems.