System locking up when running Access 2007 query

Morning All,

I've encountered this issue before and I don't know how it goes away.  When I run a query in Access against my mainframe system the query appears to lock up.  When it does display the results, it doesn't allow you to click into a cell because it's still running.  It would appear that it's a memory issue on my side but I have 8Gb's of ram in my CPU.  

My query is taking a linked table from my main frame and using a list of ID Numbers from a separate table I've imported from Excel to do a match.  When it finds the match it outputs three additional columns from the mainframe.  Does anyone know why this would happen?

I'm running Windows 7 Professional 64bit, Office 2007, i3 Processor, and 8 gb's of ram.  
LVL 1
Anthony6890Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Jeffrey CoachmanMIS LiasonCommented:
<I've encountered this issue before and I don't know how it goes away.>
Check your network traffic at the times it runs slow...

Only this one query?
If you delete, then recreate the query, and run it, what happens?

What if you run the query on another machine?

How complex is the "Matching" logic in the query?
How many records are you dealing with?
Geographically, how far away form your machine is the main frame.

What are the network specs?
Anthony6890Author Commented:
Yeah I've considered network traffic being an option.

It's not just this one query, it can be others.  I haven't encountered it in a while- but when I do it really bothers me and slows me down.

If I delete and recreate it the same thing happen.

I have to try it on another machine.

The matching logic is extremely simple.  I am just matching two values that are numbers- customer ID numbers.

I'm dealing with about 16,000 records.

I'm about 50 feet from the mainframe.  
Jeffrey CoachmanMIS LiasonCommented:
Then to me, this would point to a networking traffic issue..

(Or an intermittent networking connection perhaps)

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

Anthony6890Author Commented:
I'll look into my network connectivity...
kmslogicCommented:
Posting the actual SQL here never hurts
Anthony6890Author Commented:
It appears that it was my networking connection.  Because my network cable goes into an IP phone first and then to my nic card- that apparently had been the issue.
Jeffrey CoachmanMIS LiasonCommented:
thanks
Anthony6890Author Commented:
No, thank you.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.