ACC: Microsoft Access May Choose an Unexpected Index as the Primary Key

MORE INFORMATION

Steps to Reproduce Behavior

1. In a Microsoft SQL Server utility (such as isql/w), run the following commands:
   

         CREATE TABLE tblPKTest
          (
             ID int Primary Key Nonclustered,
             Fname varchar(50) null,
             Lname varchar(50) null,
             Field3 varchar(50) null
          )
         go
         CREATE UNIQUE INDEX aaa on tblPKTest(Fname,Lname)
   						

2. Start Microsoft Access and create a new database.
3. On the File menu, point to Get External Data, and then click Link Tables.
4. In the Link dialog box, click ODBC Databases in the Files Of Type box.
5. In the Select Data Source dialog box, click the data source to connect to your SQL Server database, and then click OK. Supply any necessary log on information, and click OK.
6. In the Link Tables dialog box, select the tblPKTest table created in Step 1, and then click OK.
7. Open the linked tblPKTest table in Design view; click Yes to the prompt that you cannot modify all properties of a linked table. Note that the PrimaryKey is not the ID field as expected, but the combined index of the Fname and Lname fields.