Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
ODBC Connection ... is busy
Message
 
À
07/04/1999 14:00:31
Information générale
Forum:
Visual FoxPro
Catégorie:
Client/serveur
Divers
Thread ID:
00205649
Message ID:
00206297
Vues:
19
Xavier,

You need to set the view's fetch size before you open it. What's happening here is that when you use the view its fetch size is probably 100 (the default) so execution continues after the first 100 records are retrieved. Setting the FetchSize to -1 at this point will only have an effect if you requery the view. Instead what you need to do is permanantly set the view's fetchsize to -1. If you created the view with the view designer, open it in the designer and choose advanced options from the query menu. Click All for the number of records to fetch at a time. You can also do this in code with:

DBSETPROP('ViewName', 'View', 'FetchSize', -1)

>Hi,
>
>I have tried the code below but I still get connection busy on line delete for
>
>Can you help ?
>
>Thanks
>
>
>SELECT SELECT(1)
>USE Jwiplab
>=CURSORSETPROP('FetchSize',-1)
>GO TOP
>DELETE FOR job = curjob
>=TABLEUPDATE(.t.,.t.)
>
>
>>Xavier,
>>
>>ODBC only allows one command to execute at a time over a single connection. If you're using views and you have the FetchSize for the view set to anything other than -1 you can get into a situation where one view is not done requerying when you try to requery or update another view. The easiest thing to do is to just set the FetchSize for each view to -1.
>>
>>>Hi there,
>>>
>>>I am using ODBC to SQL Server to update a few tables. When i run my update prog. I get this error message after a while connection ... is busy. What does it mean and how can I avoid that.
>>>
>>>Many thanks
>>>
>>>Xavier
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform