Yes, removed awhile back and tested many times since then with no luck. <g>

I was trying different settings on UseCursorSchema. Right now it's back to true with no appreciable difference.

Do you think it would matter if PAYMENTS.PAYID is not set up as a PK in the underlying Access table? But that wouldn't affect why it's not building an update command.

>Did you remove your UpdateCmd property setting that you had added?
>
>BTW, in the code Naomi posted, you have UseCursorSchema = .F. but it normally should be .T. unless you are adding the flag on the CursorFill() command that says to use CursorSchema.
>
>>You think? <g> I thought so, too, but at present I'm not sure why it won't build the update command (which is what it would seem to be failing to do). It did make me build the JOIN condition myself, but would its inability to handle that also mean it couldn't handle building the update command? Any ideas?
>>
>>>You mean that when you Tableupdate() and stop processing in the BeforeUpdate method in your CA subclass, the incoming parameter cUpdateInsertCmd is empty at that point? That would certainly be a problem. :-)