I have an ASP.net order entry system that will occasionally insert duplcate
orders into the database. We are using SQL Server for the session state.
This also only seems to happen when the server has not been rebooted for a
long period of time. When it starts duplicating, it will do so about 3 or 4
times and it's not every order. Some will come in fine the next one gets
duped, the next couple are fine, then another dupe or two, etc. Anyone have
any ideas why this might be happening?

Thanks,

Todd

Have you considered the possible effect of a double-click? Depending on your
design it may be a possibility.

"Todd Plambeck" wrote:

> I have an ASP.net order entry system that will occasionally insert duplcate
> orders into the database. We are using SQL Server for the session state.
> This also only seems to happen when the server has not been rebooted for a
> long period of time. When it starts duplicating, it will do so about 3 or 4
> times and it's not every order. Some will come in fine the next one gets
> duped, the next couple are fine, then another dupe or two, etc. Anyone have
> any ideas why this might be happening?
>
> Thanks,
>
> Todd
>
>
>

"Todd Plambeck" <(E-Mail Removed)> wrote in message
news:%233$(E-Mail Removed)...
>I have an ASP.net order entry system that will occasionally insert duplcate
>orders into the database.

The only thing to prevent duplicate data record is to designate a field
within the Order table as Primary Key/Unique and not null. Then trap the
insert command to see who causes that !

> We are using SQL Server for the session state.

This should be fine. I am using this too and found out that it is very
reliable. Performance is not that bad!

John