Disclaimer: The information provided on DevExpress.com and affiliated web properties (including the DevExpress Support Center) is provided "as is" without warranty of any kind. Developer Express Inc disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.
Confidential Information: Developer Express Inc does not wish to receive, will not act to procure, nor will it solicit, confidential or proprietary materials and information from you through the DevExpress Support Center or its web properties. Any and all materials or information divulged during chats, email communications, online discussions, Support Center tickets, or made available to Developer Express Inc in any manner will be deemed NOT to be confidential by Developer Express Inc. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.
As a workaround the unbound column feature can be used.
Please refer to the following tutorial:
http://demos.devexpress.com/Tutorials/Grid/Binding/CompositeKey/CompositeKey.aspx
Please refer to the additional tutorial (How to modify data when a composite key is used):
http://demos.devexpress.com/Tutorials/Grid/Editing/EditingWithCompositeKey/EditingWithCompositeKey.aspx
The following KeyFieldName will be valid starting with 2009.1: "column1[;columnx]". For example: "FirstName;LastName;Phone;BirthDate".
Please Note:
We do not do any performance optimization for the Server Mode. This means that although Server Mode supports composite keys, it will work VERY slowly, so basically you it's a recommendation to use the Unique key field as the KeyFieldName.
Since this is what XPO requires for best performance and in our experience most databases with large amounts of data have a unique key field, we do not consider this a big problem and we have decided not to spend more time on it.
To learn more about "Server Mode" please go Server-side Data Management.
Than you,
Andrew R&D.