So to address this I tried including the two fields I set as keys in the FieldsToExcludeFromUpdate list and tried my update again.  This time I get an error about keys not existing in the table.

What am I doing wrong here? 

I presume you know that SF will handle the CRUD without the use of stored procedures. I can imagine this may not be an option for you, i.e. your shop mandates procs, just thought I would mention it.

Cheers, Peter

Trying to update a record I recieve the following error:"Cannot create UPDATE command because a business object with PrimaryKeyIsAutoIncremented = True must have exactly 1 primary key field"

This error makes sense since I have specified two keys for the table I'm updating.  Now I'm not here to discuss the merits of combined keys (not my database design) I'd like to know how to best handle this situation.  If I don't specify both fields as keys then the delete SP call does not send both fields.  If I do set up two keys then I get the above error.  And since the database is most definatly handling the field incrementing turning that off seems a bad idea.  Is there an easy way around this or do I need to go hog tie our DBA?  btw, if it matters this is Oracle (of course).

thanks