Originally posted by Wokawidget
Adding an identity field to a DB is dead easy. It should not affect your code or require ANY changes...UNLESS the code is like:
VB Code:
  1. adoRec.Field(1).Value = "Fish"
In which case you will get an error as Field 1 is the Identity. Same goes for inserts and updates...
It may be a bigger pain if you want to implement it late on in the projects design and you will have to rewrite alot of existing code to accomondate these changes, but you could knock up a few classes that loaded 100k's or records 100 by 100, in say an afternoon....no problem, so the fucntionality isn't hard, what is is implementing as I know it would be a bugger to add that type of functionality into our apps. But yes I agree with you that implementing into a large system may cause a few problems, but from scratch, there is no problems what so ever.

Another good discussion...
****! Am late for the pub!!!
Boooooooooooooooooooooo

Woka
Well - Most of our New systems (infact all - no vb dev.) are web based systems so these problems are not as big now. Its just something that i struggled with about 3-4 years ago.

Anyway - Good Discussion.