>> add a column for it, but don't use the PK. That will require creating another table to handle the numbering for your application plus coding to handle the incremented value in that column, well, simply, I don't bind the PK, I handle it manually.

>>at most, it's only used for display. It's not something the user can edit. I display it in a label It can be used for entering a number to search for, so I don't bind the PK to a textbox, I handle it manually.

Binding is Good(Less coding) and Bad(more code to control) If you want full control on your form workflow, don't use binding If you bind a control (textbox) to datasource (access or mssql) to field ID (AutoNumber) and you want to add new record, the textbox will display -1 (you have more coding to prevent it) sometimes you will not be able to leave textbox binded to numberic (int,dec) empty (blank), unless you enter a value (you have more coding to allow it) binding is powerful and easy if used with dataset, but not easy if used with LinqToSql or EF In my form, I use binding and manual where necessary.