>that's right!!! It's one of 3 executables that we have given them and they can run the other two - no problems. It's just the admin.exe that's causing the problem. None of our other offices (same OS Win 2000) are experiencing it... it seems to be just this one office.

If your Admin.Exe is in a seperate directory, you may have a corrupt Foxuser table. Or some corruption elsewhere that only the Admin uses at startup.

Tracy