>It's been a while so please help me wrap my head around this.
>
>I want to use updateable remote views against a sql backend that has compound integer keys on some of its tables.
>
>In this case I have a remote view that joins Product_in_Future_Change with Product on Product_id.
>
>But Future_change_id and product_id make up a compound key on PFC, which is the table will be updating.
>
>For purposes of pulling data to be updated with this view I want all the records with a FC_id ( ie. for all products )
>
>Of course I will not be changing the prod_id in the record
>
>When I save to the backend from this view, does the sql passthrough that gets sent know I am using the compound key in order to match my record with the record on the backend?
>
>(It would seem they should but in the past I have always been able to design my own schema and I hold as an article of faith that compound keys are almost as evil as non-surrogate keys )
>
>TIA

I don't see why it should be a problem. If you set your key correctly, then, IMHO, it does not matter if the key is compound or single field.