Yeah, I caught that one quick. And disabled it quick. Only problem is that it happens a lot when trying to open a file in Word directly. The only weird consistent thing is that it only happens with a 2000 server doing the file serving, never when linux is doing the serving. -=shrug=-