Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
CursorAdapter question
Message
Information générale
Forum:
Visual FoxPro
Catégorie:
Base de données, Tables, Vues, Index et syntaxe SQL
Divers
Thread ID:
01204556
Message ID:
01206881
Vues:
19
Please note that I said "seemed to be a bug in either the CA or in ADO." I do know that 1) two KB articles related to ADO 2.7 bugs directly applied to my exact situation and 2) I could get the underlying tables to update in other setups but not when I joined these two tables. This was a simple join of two tables on one field with a simple WHERE clause and pulling only six fields. Was it a bug in ADO or the CA, for sure? No, I can't say that, so I used the word "seemed." And I'm using ADO 2.8, but I don't think the KB article said the bug had been fixed. In any event, since I don't use CAs that much and ADO even less, it seemed better to go with my workaround rather than to keep trudging down a path that might lead nowhere.

As for the ADODB.Command object, I wish the VFP docs would give more concrete examples, but I guess that's water under the bridge.


>So, a bug in either the CA or in ADO is the only alternative? You are 100% sure that the recordset is properly configured? See if thread #898887 can help.
>
>There is always an option to use ADODB.Command object to modify the backend, CursorAdapter supports this too.
>
>Thanks,
>Aleksey.
>
>>Well, the problem seemed to be a bug in either the CA or in ADO. Some KB articles on ADO 2.7 indicated problems in situations the same as mine, however I have 2.8 installed. Maybe it was not fixed. I could update the underlying table only when the cursor created by the CA was not the product of a join. So I opened two tables, one to help with letting the user edit the data and one to actually get the data updated. Works fine, though it's a bit kludgey.
>>
>>>Hi Russell,
>>>
>>>When you are using “ADO” data source, Update/Insert/Delete commands are not generated and are not used unless corresponding …CmdDataSource property is set to ADODB.Command object and …CmdDataSourceType is set to “ADO”. When commands are not used, all modifications go through the Recordset object and you should make sure that the Recordset is configured in a way that it is capable to perform required modifications.
>>>
>>>Thanks,
>>>Aleksey.
eCost.com continues to rip people off
Check their rating at ResellerRatings.com
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform