David,

I subclassed the CA, then built the CA for the form on that subclass. It's all done via a VCX - I try to avoid PRGs when I can. I'm using the builder and checking the checkboxes for the PK and the updateable field. I'll take a look at what you suggest and post again later.

Thanks,

Russell

>Russell,
>
>>I am only updating PAYMENT.PAY_STATUS, so I marked PAYMENT.PAYID as the key field and made PAYMENT.PAY_STATUS an updateable field.
>
>Let's start with this part of it. How did you mark payid as the key field and make pay_status updateable, specifically? Is this CA definition in a VCX or coded in PRG? If PRG, please show the property settings of CA.
>
>How about defining a CA as a subclass of CA baseclass and put some code in the BeforeUpdate method so you can look at the incoming parameter "cUpdateInsertCmd" (what VFP has created to send through to the backend when you TableUpdate())? That might give a clue as to the problem.
>
>Of just start out by instantiating your CA (however it is defined -- but without your custom UpdateCmd) and showing us the output of:

? oCA.DataSourceType
>? oCA.SelectCmd
>? oCA.CursorSchema
>? oCA.Tables
>? oCA.KeyFieldList
>? oCA.UpdatableFieldList
>? oCA.UpdateNameList
>

>I also urge you to trap the BeforeUpdate and show us the value of cUpdateInsertCmd inside that method/event call. That's the best place to see what is happening if it gets that far without throwing the error (I'm pretty sure the error is happening later when that command actually gets parameterized and sent on to the Access driver).