Try to assure that the servers and desktops have UPIs and never let anyone cut corners with your network hardware. Sometimes a second voice (net work engineer ) can help isolate problems. Also - maybe once a week, the CDX tags should be deleted and rebuilt. Even big 24/7 SQL shops will take an hour off every week to "groom" the files!:)

>>Quite possibly a file or index corruption that database validation didn't catch and/or a FOXUSER corruption (if SET RESOURCE is ON).
>>
>>VFP8 and 9 support a SET TABLEVALIDATE setting that can catch (and help resolve) a lot of these issues.
>
>Thanks everyone. One of our tables/index was corrupt, but validate does not catch it. Do you all recommend we certainly update from Fox7 to Fox8 or 9?
>
>We discovered that Win2003 server actually has TWO registry settings to denote if Op-Lock setting is enabled or disabled. Also, my server coworkers just told me Op-Lock was ENABLED. Do you think this lead to the corruption?
>
>We definately need to DISABLE Op-Lock... correct? This has fixed issues for us on WINNT and WIN2000 server.
>
>THANKS ALL