>Hi,
>
>We have some problem running a shared tables on a specific network (Solstice) and are trying to find a solution.
>
>The problem occurs when two users are updating the same table, as the changes made by user A does not get through to user B and the other way around. And if they continue to make changes to the file the program generates a General Program Failure.
>
>A difference we have found between this network and other is that the client OS does not receive the proper modification date for the file from the server. Looking at the file in the Explorer, after updating the info, we see one modification date on the file, but looking at the preferences of the file we find another, later, modification date.
>
>We are therefore wondering if anyone knows if Foxpro is using the modification date of the DBF file in handling changes to the file. If this is the case, the General Program Failure might occur when Foxpro is trying to flush cached data to a file modified by another user, although it does not seem to have been modified when checking the modification date.
>
>Any experience with Solstice or the way Foxpro is updating DBF files is greatly appreciated...


I don't have any experience with Solstice, but I have had data problems on Novell and NT when using write caching. Turning off all write caching on the drive controller fixed the problem.