Michel,

I'm no guru, but I have worked with dbf style Db's since way back when it was still called dBase2 - and in my humble opinion for what it's worth, the answer to your final question is no.

HTH

>I would like to gather some feedback on some potential infrastructure on way to access and write data into a backend when the requests are coming from various servers.
>
>Before, the client was using a direct map drive shared to insert and update data into another server. In such a situation, the client reports that several corruptions happened when specific PCs were doing some inserts and updates.
>
>In the actual setup, we have a .NET Web interface, several .NET desktop applications and several .NET Web Services that are located on various servers which would all use the same backend located into a dedicated server serving that purpose. The backend is still Visual FoxPro. For our first phase, it is expected that the backend remains Visual FoxPro. In all those applications, the data provider is OleDb.
>
>If we keep that design, is there any factor that could cause data corruption such as when it was happening when the previous versions of several applications were using a map drive for the data access? Basically, are we in better shape to avoid those situations now?
>
>The client reports that if we would use SQL Server, Oracle of Sybase that the opening and writing mechanism to write to the tables is done from a service which does it all on the server. I understand that this prevents those unexpected situations of data corruption. But, this does not apply when the backend is Visual FoxPro. So, is there a way to be safe in regards to data corruption using Visual FoxPro?