1) No, I do not use an async connection, .F. = synced, right?

2) Tried both suggestions

DOEVENTS, it still goes into a forever loop
Timeout of 10 seconds in the wait window - Connection busy error.

All this used to work fine when I had only one connection in the VFP DB, just USE tbl1 in 0 a.s.o.a.s.f.

Then my client decided that he needed two identical SQL Server DB's to which the interface has to connect, so i put in the USE...CONNSTRING Connect1,.T.
or Connect2 respectively, depending on a choice in the main forms menu.

Could this have something to do with private datasessions and the SET DATABASE command, which scopes to the datasession?

Any and all ideas are welcome, I really really don't want to have to rewrite the whole thing with SQLPT.

BR

Peter


>You use a async connection ?
>
>your cycle saturates the cpu.
>
>Use, and move the mouse:
>

>DO WHILE SQLGETPROP(lnSql,"ConnectBusy")
>  DOEVENTS
>ENDDO
>

>or
>

>DO WHILE SQLGETPROP(lnSql,"ConnectBusy")
>  wait windows "Wait download" TIMEOUT 0.1
>ENDDO
>

>
>Fabio