PDA

View Full Version : MS Office Slow to Respond

Tr1cK
08-07-07, 09:53 AM
I have an HP here at work with a 2.4ghz A64 single core and 1gb DDR2. It's running XP pro and using Office 2003. When I open an office file (most of the time a Word doc) it is very sluggish. I can deal with that. The real problem lies in me switching between windows and every time I go back to the Word window, I get the hour glass and have to wait like 20 seconds before I can do anything in that window. I can go to other windows and do things, but working in Word is a no go until I wait for it to respond. The documents I work on are on a remote server across the state, but I would think that they would cache locally when I open them. I am within a gnats ass of removing it and dropping open office on there, but some of my representative pricing programs might have a fit. I know they don't like not having adobe pdf reader on there because I did try foxit before and had issues.
evilghost
08-07-07, 09:55 AM
It's probably re-polling the document for any changes since it lost focus. I'd imagine it's annoying; copy it to the local machine prior to opening it.
Tr1cK
08-07-07, 09:57 AM
It's probably re-polling the document for any changes since it lost focus. I'd imagine it's annoying; copy it to the local machine prior to opening it.

So basically it's because the server is non-local? crap.
evilghost
08-07-07, 10:04 AM
So basically it's because the server is non-local? crap.

You could always try Open Office.

I bet it's creating the ~TMP recovery/working file on the server share instead of the local machine.
Tr1cK
08-07-07, 10:10 AM
You could always try Open Office.

I bet it's creating the ~TMP recovery/working file on the server share instead of the local machine.

After checking, yes it is. Any way to force it to create it local?
evilghost
08-07-07, 10:19 AM
Tools -> Options -> Save

Enable the "Make local copy of files stored on the network or removable drives"

See if that fixes it. You'll have to close/re-open Word.
Tr1cK
08-07-07, 10:27 AM
I was certain I had it checked, but it was not. Time to test....

Well it just seemed to make it worse. I guess I need to check with the guys about making the server a bit more local. It is across the state, but you would figure with high speed connections that a 100kb file would take more than a second or 2.