We think it's the in memory index corruption because of caching which VFP 8 now reports butVFP7 ignored. We're going to use SYS(1104) in the error handler with a retry on the LOCATE. The description of the problem in earlier threads matches our problem.

My sister managed a big Fox app on a Novell a couple years back - index corruption was a nightmare then for her. My systems were on NT, no problems. She was so jealous! Especially after rebuilding a 3 million record customer table with about 20 tags every night for months.

Thanks Jim


>David,
>
>Is it possible that there's WRITE cacheing on the server's DB HD?... or even on workstations? I don't know anyone who trusts that stuff and turning it OFF seems to be pretty much universal.
>
>I recently had a problem where network adapters had 'sleep mode' set on at factory (all DELL systems). a sudden short-term sleep might do who knows!?!?
>
>Finally, long ago and with a different NOS (Novell 3.11) we had daily index corruptions. These were real. We had the most expensive server available at the time, a Tricord model XXX. Turned out it had never been 'certified' for Novell. Changing to a clunky sounding (by comparison) Compaq ??? pentium 90 with 256MB and a 20+ drive RAID array solved that one nicely.
>
>One more thing... I wonder if older OS' on workstations might have some compatibility problems with latest storage/locking scheme of 2003 server.
>
>good luck
>
>