This is intriguing, Bill.

Some other things that come to mind:

1) Can you turn disk WRITE CACHE off on all workstations? that might influence things.

2) Are your W2K systems ALL up-to-date as regards SPs? There was a known problem with buffered data being lost on power-down that was fixed, in, I think, SP3.

3) Is it possible that someone is accessing the data outside of the application and doing something odd or possibly ill-timed?

4) Is there some table (or related CDX/FPT) that is near the size limit?

5) Possibly some flakey network connection. Maybe a recently installed workstation, or maybe someone recently added a coffee heater or other electric device to their workstation that is causing interference or maybe some other business device recently installed that is causing interference.

again, good luck



>Jim -
>
>Thanks again.
>
>The corruption problem is the primary issue. THat device is an Iomega NAS device running W2K, clean as it comes from Iomega. They don't support updates from MS so that isn't the problem.
>
>I thought we'd solve the corruption problem when we moved the app and data to another server, but late today we had another incident, certainly less than it was, but still there.
>
>We're an entirely W2K shop, XP is only deployed on the test bench and not with this app at present.
>
>All of our VFP apps are running fine, no problems, not even a hic-cup, and on both of the servers in question. The problem seems to be limited to this one FPW26 app, and even then it's a pretty random event.
>
>I suppose we could be having some bizzare problem in the switch tower but I'd think we'd be seeing a more widespread data issue accross applications.
>
>Thanks again for tossing this around with me.. it's all helpful.
>
>-Bill