That's a good question I don't know the answer to. I've seen terrible slowdowns opening/saving Office docs on XP (30 seconds to 5+ minutes) and slowdowns while entering data e.g. user types several words in Word, they are not displayed for over a minute. These slowdowns are not consistent. I've made these problems go away on a couple of networks by following the W2K DNS setup recommendations as linked below.

I think on some networks, incorrect DNS setup is being masked by the sheer speed of modern computers. If you've got a network with fast XP Pro workstations and a good W2K server, on 100BT networking, lightly loaded, users don't complain too much if it takes 2 - 5 seconds to open a small Office document. When properly configured, such operations are nearly instantaneous.

Having said all that, I don't know if a 16-bit FPW app would be more, or less, affected than 32-bit VFP, or 32-bit Office.

>Wouldn't name resolution problems also be reflected in his VFP6/7 apps also?
>
>>Take a look at FAQ#15468
>>
>>Also, IME XP is much more sensitive to DNS settings than any earlier OS. This seems especially true if the workstations are members of a domain. Ideally, all XP workstations should have their DNS server set strictly to a Windows 2000 DNS server, which is configured to forward requests as necessary. I don't have any experience running XP workstations against an NT4 server but it's something you might try.
>>
>>A KB article on W2K DNS: http://support.microsoft.com/?id=291382