Okay, I've read this entire thread, but I'm still trying to understand what the 'final' solution is.

I can see that there is a problem with roaming profiles on a network that has a mix of WinXP and Win2K workstations. A user that logs in on an WinXP computer experiences this problem the next time he/she tries to run VFP on a Win2K workstation.

One solution that I see is to delete the profile from the server and from the workstations and create a new one. One that is not mentioned is the brute force method: turn off roaming profiles for anyone that has this problem. (Not always practical, I know.)

So has anyone yet determined what is 'damaged' (or altered) in the profile when a user logs in to WinXP? Is there any other solution than deleting the profile and starting over? I've got several users on my network that have this problem and I expect it to continue/grow for a while. Our network group is planning on replacing Win2K workstations with WinXP workstations by attrition. So any solution would be most welcome.

John