Can anyone tell me why the BLG would be generating the wrong primary key for certain tables? It seems to be happening only on my code tables that are using the @Name for the description that can't be null. When I look at the design of the database, the primary key is correct in the database with the @StatusID (for e.g.) being the listed primary key. I noticed this also on another table that I generated over a month ago.

It appears to be using the clustered index in order to generate the SelectPK stored procs. Is there a way to override this behavior?