Hi Al.

Thx for your response. Most of my clients run NAV, but none are yet to switch over to Win2K (or NT4 w/s) so I have not been able to evaluate this first hand. The hardware we have in place just isn't *beefy* enough overall in order to absorb the performance hit of running NT4 .. 5 . 2000 w/s (whatever you want to call it) - over Win98.

Like most everyone in the world, this will evenutally occur to us, so I am interested in this problem.

To be clear, though, your experiences with this problem are that is specific to Win2KPro? If so, it surely begs the question of why does NAV behave this way with VFP on Win2kPro only?

Or perhaps is it the Win2K server or a combination of both?

Thx for the info.

A round of hardware upgrades are in the cards for us and this might bite me!

Scott

>If NAV AutoProtect is network-aware it might be locking server files. It may also be scanning local temp files VFP uses to buffer network files and increase performance. Only Symantec knows for sure.
>
>Since it's a piece of consumer software over which we have no source code control, it's more important to identify what we *can* do. As I see it, in descending order of preference:
>
>- configure AutoProtect to exclude all VFP file types (temporary files too)
>- disable AutoProtect
>- uninstall NAV