Online form Submission ISSUE

"Will Thread.Sleep will be my answer"
No. All that would do is move the problem to collide with a different user.

There are a number of ways to handle this. The simplest in terms of implementation is to set the ID field to Identity - which means that SQL becomes responsible for allocating it a value, and you just have to modify your code to not try to set it. However, this has the drawback that you need some means of finding out what value was assigned if you need to cross reference this to any other tables. This means moving your insert into a Stored Procedure which does the insert and returns the Id value in the same operation, or reading the record back after the insert to find out what value was assigned. Which means you need to have a way to find it as a unique row...

The other method is not to use a integer ID, but to use a Guid instead. You assign the Guid ID in your application, and set it when you insert the row. Since the chances of generating two identical Guids is slightly lower than those of winning the lottery every single week for a few years it is a simple way to do it, and is generally the approach I take. It can mean more extensive changes to your software though, depending on how well you wrote it in the first place! :laugh: