I have a DB2 standard table (non-recnum), with 2 indexes defined on it. Both of them could be used to uniquely identify the record. (actually, almost every index created for DF apps could be used for that, as they need to be UNIQUE, but that is a topic for some other day conversation. )

Ok. Index-1 the real PK, was properly identified by CK as the Primary-Key .

But the CK insist in setting the PRIMARY_INDEX table attribute to index 2.

I can force it to be Index-1, and DF makes the proper modification to the int file. But if I perform a simple refresh on this table (not a full Connect), the PRIMARY_INDEX table attribute is set back to 2 again.

Click image for larger version. 

Name:	Primary-Index_vs_PK.png 
Views:	110 
Size:	72.5 KB 
ID:	10715

The Index-1 properly identified as the PK.
Click image for larger version. 

Name:	Index1_as_PK.png 
Views:	105 
Size:	41.5 KB 
ID:	10716

Table's INT file:
Code:
DRIVER_NAME DB2_DRV
SERVER_NAME DFCONNID=RVMEDREP_ConnID
DATABASE_NAME GROUPMENURIGHT
SCHEMA_NAME APPCTRL

RECNUM_TABLE NO
PRIMARY_INDEX 2
TABLE_CHARACTER_FORMAT ANSI
USE_DUMMY_ZERO_DATE YES
IDENTITY_CACHE_SIZE 0

FIELD_NUMBER 1
FIELD_INDEX 1
FIELD_RELATED_FILE 6
FIELD_RELATED_FIELD 1

FIELD_NUMBER 2
FIELD_INDEX 1
FIELD_RELATED_FILE 5
FIELD_RELATED_FIELD 1

INDEX_NUMBER 1
INDEX_NAME GROUPMENURIGHT_PK

INDEX_NUMBER 2
INDEX_NAME GROUPMENURIGHT002
Shouldn't be the case to have some kind of consistence between them ?

Regards