RE: Error 1541 - connection busy

Tech-Archive recommends: Fix windows errors by optimizing your registry



Hi Paul:

This may just be an information error saying that you need to wait until
the connection is not busy, which may be just a micro second longer.

You need to capture this error in your error routine and use the INKEY(0.5)
function (0.5 is a half of a second) before the RETRY command, or you can
use the SLEEP API to wait for a period of time before the RETRY command.

* Place the DECLARE line of code in your main program if you want.
DECLARE Integer Sleep IN Win32API Integer
* Call the API whenever you want a wait state.
=Sleep(500) && Pause for a half second, a whole second is
1000
(milliseconds)

Personally, I would use the FoxPro INKEY function because it has been in
FoxPro for years. You may want to try INKEY(0.1) - 1/10th of a second
because the wait timing is a part of testing to see what works best for the
app.

I hope this helps.

This posting is provided "AS IS" with no warranties, and confers no rights.

Sincerely,
Microsoft FoxPro Technical Support
Lee Mitchell

*-- VFP9 HAS ARRIVED!! --*
Read about all the new features of VFP9 here:
http://msdn.microsoft.com/vfoxpro/

*--Purchase VFP 9.0 here:
http://www.microsoft.com/PRODUCTS/info/product.aspx?view=22&pcid=54787e64-52
69-4500-8bf2-3f06689f4ab3&type=ovr

Keep an eye on the product lifecycle for Visual FoxPro here:
http://support.microsoft.com/default.aspx?id=fh;[ln];lifeprodv
- VFP5 Mainstream Support retired June 30th, 2003
- VFP6 Mainstream Support retired Sept. 30th, 2003

>I have Form 1 that calls Form 2. When that call is made, I get Error 1541
-
>connection busy. I can't tell exactly where it's happening, because the
>error occurs in "Line 0". If I choose "Ignore", Form 2 opens and runs
>properly.

>The forms have nothing in the de; all data is opened in form.load. Both
have
>private data sessions. The data is all in MSSQL, which I access via remote
>views based on a connection to an ODBC source.

>Naturally, the error occurs only at the client site, and not on my own
>network.

>Might this have something to do with the SHARE clause in the view creation
>statement? Some views were created in the view designer, which as far as I
>can tell, has no option to set this clause, and others were created in
code,
>some with SHARE and some without. The description of the SHARE clause of
>CREATE SQL VIEW in the FoxPro help file is not at all clear to me.

>If this is what's causing my problems? Is it possible to set the SHARE
>attribute in the view designer? Why does it work on my network but not on
>the client's?

>Any other suggestions?


.



Relevant Pages

  • Re: Error 1541 - connection busy
    ... This posting is provided "AS IS" with no warranties, and confers no rights. ... Microsoft FoxPro Technical Support ... while sharing a connection handle. ... > Microsoft FoxPro Technical Support ...
    (microsoft.public.fox.programmer.exchange)
  • Re: Error 1541 - connection busy
    ... Any comment on my questions about the SHARE clause? ... > the connection is not busy, which may be just a micro second longer. ... > Microsoft FoxPro Technical Support ... Some views were created in the view designer, ...
    (microsoft.public.fox.programmer.exchange)
  • Re: CUPS (Sid) not printing. (SOLVED?)
    ... The epson lq570, 223, on-line. ... At least it shows the parallel port is ... Physical connection: ... 127, busy, out of paper, on-line ...
    (Debian-User)
  • Re: fax connection
    ... connection altho the only option I see is 56K modem. ... You cannot send faxes over a DSL connection as such. ... I always get a 'line busy' response when sending a fax. Whats wrong? ... internet connection. ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: Error 1541 - connection busy
    ... while sharing a connection handle. ... > * assumes local server, change to machine name if server is not local. ... > Microsoft FoxPro Technical Support ... >>Any comment on my questions about the SHARE clause? ...
    (microsoft.public.fox.programmer.exchange)