Information générale
Catégorie:
Bases de données DAO/RDO/ODBC/ADO
The reason I mentioned an identity (which is not a datatype, AFAIK) field is because I was expecting the properties to somehow indicate that I can not write to it, basically bits 2 and 3 set to 0. Instead I'm getting a value of 24, that is bits 3 and 4 set, indicating the field is of fixed length and the provider can not determine if it can write to the field or not (not very informative), I'm getting this value for all my numeric (integer) fields and a value of 8 (unknown updatable), for varchar type fields.
What confused me the most was the value of 32792 which is not even documented, but that went away by changing the cursortype property (Not that anything in the help file mentioned it had any effect). Now I'm getting documented values, useless nontheless.
Why do I need to know this?
I have a form method that passes the data from a VFP cursor to an ADO recordset, by looping through the fields. My problem is with identity fields because they're value is automatically generated by SQL Server, so an attempt to write to them generates an error ("Multiple step operation generated errors ..."). If anyone knows of a way to do this please let me know.
The problem is that I'm not sure what to expect from the attributes property since all I have is an example for a character field, in the example bit 3 (Unknown updatable) is also set.
>You seem to mix 2 things:
>-Identity is a datatype.
>-Updatable is a field attribute.
>
>What is your exact question?
Précédent
Suivant
Répondre
Voir le fil de ce thread
Voir le fil de ce thread à partir de ce message seulement
Voir tous les messages de ce thread
Voir tous les messages de ce thread à partir de ce message seulement