>>>>Hi,
>>>>
>>>>I am trying to determine if how I am building values for properties UpdateFieldList and UpdateNameList for a CursorAdapter has a downside.
>>>>
>>>>What I am doing is dynamically (when creating a CA for a table) build the values of these properties bases on the structure of the table and include
all columns of the table. That is, I do not exclude the PK column or any other column. Is there a potential problem with this approach?
>>>
>>>Yes, you should EXCLUDE the PK field from the list. If PK is identity field you can not update it anyway.
>>
>>But UpdateNameList must have PK field, otherwise, updates won't work; isn't it correct?
>
>Did you try using Mark McCasland CA builder? It automatically constructs the commands based on all columns in a table.
>
>Try it as a sample.
No, I didn't try his example because I thought it was for building CA in design time. I prefer to build the properties at run-time dynamically. But, to my question, was I correct that PK must be in the UpdateNameList?
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
