In order to support multiple-key field scenario you don’t need to set the DataKeyField property in the WebGrid table. A sample, HierarchicalGrid.aspx, in WebGridSamples project shows that the OrderDetails table has multiple-key – OrderID and ProductID –, so in the OrderDetails WebGrid definition no DataKeyField property is assigned.

<ISWebGrid:WebGridTable Caption="Order Details" DataMember="Order Details">

On the other hand, the Order table which has the primary key OrderID will have to be assigned the DataKeyField property.

<ISWebGrid:WebGridTable Caption="Orders" DataKeyField="OrderID" DataMember="Orders">

This should helps.

Hello,

It should be no problem when have 2 primary keys in your table. When bind with 2 primary keys/composite keys, WebGrid would automatically detect it. You would not need to specify DataKeyField properties.
Please see my attached sample. It should work fine. For Add,Update and Delete scenario, you should use Optimistic Concurency in your SQLDataSource.

Regards,
Handy

I am sorry ,I can not use your database.Could you please give a  sql2000(or sql2005) database.
Please see the picture!

My sql is:sql2005

Hello,

Unfortunately, I could not downgrade sql in here. You can try to create a simple dummy database such as the structure and run it. It does not cost big effort since it is only a simple table.

Regards,
Handy