Josh,

Do you use exclusive access in your application or does it only occur when only one user is in the system ?

The solution to the problem might be to prevent VFP to chache updates. this can be done in several ways:

- Don't use exclusive access in tables
- Be sure someone else is using the tables too. (forcing VFP to inmediately writeback changes)
- On the NT server disable exclusive oplocking (changing /modifying a registry key, but I forgot which one it was, maybe someone else can tell).

Walter,

>>Are you using a slow network connection by any chance? Or did you modify a lot of data ? It seems that VFP has problems in writing the cached data to the disk or network.
>
>I think that's what it is... We ran the program on a local machine and it worked fine.
>
>>Tell me, was it slow again on the FLush or CLOSE DATA. or are things a bit
>I put flush's after every major bit of updating; and it definately "hangs" on the flush statement...
>
>-josh