Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
How to detect ADO CommandTimeout
Message
Information générale
Forum:
Visual FoxPro
Catégorie:
COM/DCOM et OLE Automation
Divers
Thread ID:
00469628
Message ID:
00470009
Vues:
35
Unfortunately, you may be out of luck here. And most likely, this will be true with the new VFP OLE-DB Provider.

This may sound goofy, but it may be worth a try... And I will disclaim this method as working since I have not tried it. If it does work, let me know..

If you really need your data in VFP, why not try using Access to link to your VFP tables. Then, you could use the Jet provider to execute your query. You might then get the services you are looking for.

Of course, if you can dump VFP as a data store in favor of SQL Server, MSDE, or even Jet for that matter, I would consider that alternative as well.

As a rudimentary - very rudimentary data store, VFP does fine. If you need some intelligence built into the back-end ala SQL, VFP does not cut it..

< JVP >




>I am using the CommandTimeout property on an ADO connection in Visual Basic to prevent queries to my FoxPro tables from running too long. This seems to work, but I need a way to determine whether a query ran to completion or timed out. I tried using the ADO event ExecuteComplete, but adStatus is always adStatusOk. I also tried running the query asynchronously (see MS knowbase article Q190606), but I get the error Current provider does not support asynchronous execution. Does anyone have an idea or a work around?
>
>Thanks!
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform