D
David M C
I've been reading lots of posts regarding not showing Primary Key autonumbers
to users. Could I ask, why is this a bad idea?
I've designed a DB for handling purchase orders. The primary key of the main
order table is an autonumber field. I use this autonumber field to generate
my Purchase Order Number in a report:
"JobNumber/AutoNumber/RequestingInitials/AuthorisingInitials".
Obviously, the autonumber increments sequentially, but can end up keaving
gaps between the numbers. Again I ask, Why is it a bad idea showing
autonumbers to users? How would you recommend generating a unique Order
Number on the fly?
Thanks
Dave
to users. Could I ask, why is this a bad idea?
I've designed a DB for handling purchase orders. The primary key of the main
order table is an autonumber field. I use this autonumber field to generate
my Purchase Order Number in a report:
"JobNumber/AutoNumber/RequestingInitials/AuthorisingInitials".
Obviously, the autonumber increments sequentially, but can end up keaving
gaps between the numbers. Again I ask, Why is it a bad idea showing
autonumbers to users? How would you recommend generating a unique Order
Number on the fly?
Thanks
Dave