The first thing I would do it's run sp_lock on SQl Server to see if users "hang" because there process is waiting for lock.

>How can we avoid “hangs”?
>The situation is: There is a client-server application. Client is Visual Fox Pro 6.0 sp 4
>Server is MSSQL 7.0. Server is Celeron 400, it’s memory is 196 MB. The example of the code is
>
>_cliptext = "select bl.cntr_num, p.pers_nm, bui.bui_adr,bui.bui_n,bl.square,bui.build_id, bl.bl_id,bl.y_debt,bl.yf_debt,bl.y_dat,bl.pay_dat as pay_dat1,bl.fine_val,p.pers_adr" + " " +;
> "from b_lease bl, person p, build bui where bl.build_id *= bui.build_id and bl.pers_id *= p.pers_id order by cntr_num"
>= SQLEXEC(Handle,_cliptext,'cursor_contract')
>…………………………………………………..
>SELECT cursor_contract
>USE
>…………………………………………………
>_cliptext = 'SELECT * from vw_b_lease where cntr_num = ?lccntr_num'
>=SQLEXEC(Handle,_cliptext,'b_lease')
>
>Usually 12 users work at the same time. Periodically users “hang”.
>It was noticed the more queries users do in the same connection the more memory is used.
>What should I do to avoid “hangs”?