Jim:
Thank you very much for your answer. We are aware of those problems, in fact we found workarounds to those although we have not ruled out that may have something to do with the freezing. Some of us think that once the sql data is in foxpro in the form of a cursor, it's basically a file and its subjected to the same problems as mentioned in those articles....Microsoft it running some special logging programs that register (supposedly) everything that happens in the background, but nothing conclusive has been found yet....

Thanks.

>Given the exposure that this problem has had at MS, the following are probably not applicable, but on the basis that you didn't mention them it might be useful for you tocheck out MSKB #818528, MSKB #294816 and MSKB #299603.
>
>good luck
>
>>W2k, the problem occurs with service packs 3 & 4, previous SP's not tested
>>
>>>What OS is running the Treminal Server sessions? Not NT I presume.
>>>
>>>good luck
>>>
>>>
>>>>HI everyone:
>>>>I have I really hard one here, so far 3 teams in Microsoft (SQL, VFP & Terminal server) could not find the problem. Also we suspect that after we reported the problem, they released (or updated) this article in the KB: http://support.microsoft.com/default.aspx?scid=kb;en-us;272756
>>>>
>>>>The actual problem we are having with the combination above mentioned (VFP/SQL server/Terminal Server) it's that out application (VFP 6.0 sp5 & SQL) which uses a combination of foxpro views and SPT, it's actually locking some tables in SQL (at least that what MS support told us) when use in Terminal Server.
>>>>
>>>>The application runs perfectly in several sites the problem it's only happening in installations with terminal services. We already had our share of problems with VFP & TS, but we were able to workaround them. Some of those problems are explained in these KB articles:
>>>>http://support.microsoft.com/default.aspx?scid=kb;EN-US;219956
>>>>http://support.microsoft.com/default.aspx?scid=kb;EN-US;258537
>>>>
>>>>The actual symptoms are as follows:
>>>>One user is searching (using a form that uses parameterized views & SPT), then probably make modifications, finally saving. From time to time at the moment the user saves (TABLEUPDATE() executed against a view), the application seems to be frozen. After that, all of the other users freeze even searching (at this point, Microsoft says that the first user has a lock in the table therefore none of the other users can even SELECT records from it).
>>>>
>>>>This problem it's killing us, because TS is our way to make out app available to different locations. We are working in an ASP.NET/VFP/SQL solution but its months away.
>>>>
>>>>Any help on this matter will be greatly appreciated.