Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Connection is busy error
Message
From
02/03/2004 05:19:44
 
 
To
01/03/2004 14:24:45
General information
Forum:
Visual FoxPro
Category:
Client/server
Miscellaneous
Thread ID:
00881990
Message ID:
00882276
Views:
28
Hi Aleksey,

Obviously having a limited imagination, I had not thought of your proposed solution.

I have not had a chance to try it, but offhand I'd say it sounds like a practical approach, so lest I forget, a heartfelt Thank you!

It's a bit weird that that changing code from
USE MyDB!View1 IN 0
to
USE MyDB!View1 IN 0 CONNSTRING lnSql
should have such a dramatic effect.

After all, it seems to me, all I'm doing is to state explicitly, what is already implied.

I can't help but wonder if programmers working with VB,C++,Java or other "real" programming languages, have to deal with similar issues?

Having spent hours trying to address this issue, I'm not in a particularly good mood, but all the same, I don't feel I'm being overly critical in saying, that it's erratic behaviour like this, that makes one wonder, whether it is sensible to keep on developing in VFP.

Just as an example, I'm still puzzled by the fact that one should be able to do things in the (although less so, still buggy) View Designer, that one can't in SQLPT, and lo and behold, vice versa.

In my humble opinion, showing all the code that's going to run, in the View Designers "View SQL" option, would be a tremendous help.

While much has been fixed over the years, there certainly is lots of room for improvement.

Boy, am I glad I got all that off my chest! :-)

BR

Peter





>>lnSql = SQLCONNECT('SomeDataSource')
>>
>>* Check for lnSql > 0, if successful
>>
>>USE MyDB!View1 IN 0 CONNSTRING lnSql
>>
>>USE MyDB!View2 IN 0 CONNSTRING lnSql
>>&& Error 'Connection MyDB is busy'
>>
>>
>>So I put in a
>>
>>DO WHILE SQLGETPROP(lnSql,"ConnectBusy")
>>ENDDO
>>
>>But that just caused the thing to go into a forever loop.
>>
>>Funny thing is, it works in the debugger.
>>
>>What to do?
>
>Hi Peter,
>
>Most likely the error is reported because the View1 hasn't finished fetch by the time you are trying to open View2. To avoid the error, execute GO BOTTOM IN View1 before USING View2 or simply change View1's FetchSize property to (-1) in DBC.
>
>Thanks,
>Aleksey.
Peter Pirker


Whosoever shall not fall by the sword or by famine, shall fall by pestilence, so why bother shaving?

(Woody Allen)
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform