>Cy,
>
>I thought using ODBC to VFP would help the corruption because my client would not be holding the file parameters that get lost when the workstation fails. Is the file header still being passed to my client and exposed to crash corruption?
>
>In your opinion, short of using sql server or other backend, what is the best data scenario (performance and reliability) for say 10-15 workstations and a NT server running a VFP app?
>
>Thanks Gary.

Well, the problem is that using ODBC is no different that using VFP natively other than its slower and you can't call store procedures. It still uses the information in the same mode.

That being said, I don't know if they are still around but there used to be a company with a product called "Advantage Database Server" which could give you the best of both worlds. You could go fully client-server with it, or use one of their hybrid solutions that let you use VFP to read the data and write to the databases in client-server mode. This being said, with our customers we have almost never had data corruption. If workstations are failing something is wrong with them and needs to be fixed. It may be that what you need to do is try different video cards as that is usually what causes a problem.