|
 |
asp_databases thread: HELP! Update concurrency error handling???
Message #1 by "Charles" <sel_rahc@h...> on Tue, 15 Jan 2002 09:03:23
|
|
Hi!
Im working on a web application that has heavy database usage by users.
Unfortunately I am running into a few problems now :(
My main problem is user concurrency in updating!
For example, if 2 users attempt to add their email address in a table at
the exact same time, one will go through while the other will recieve an
error...
How do you handle user update concurrency? I'm trying to figure out how to
handle the error(s) thrown by more than one user attempting a table update
at the same time.
I was thinking some type of 'cue' code perhaps? How do the people that
write programs used my many many users handle this problem?
Any point in the right direction, or sample code would be VERY helpful!
thank-you a TON!
Sel
Message #2 by "Julio Allen" <julioallen@y...> on Tue, 15 Jan 2002 14:50:46
|
|
Hello,
Which database are you using? If it's Access you're going to struggle with
lots of users...
Julio
> Hi!
>
> Im working on a web application that has heavy database usage by users.
> Unfortunately I am running into a few problems now :(
>
> My main problem is user concurrency in updating!
>
> For example, if 2 users attempt to add their email address in a table at
> the exact same time, one will go through while the other will recieve an
> error...
>
> How do you handle user update concurrency? I'm trying to figure out how
to
> handle the error(s) thrown by more than one user attempting a table
update
> at the same time.
>
> I was thinking some type of 'cue' code perhaps? How do the people that
> write programs used my many many users handle this problem?
>
> Any point in the right direction, or sample code would be VERY helpful!
>
> thank-you a TON!
>
> Sel
Message #3 by <odempsey@b...> on Wed, 16 Jan 2002 09:28:25 -0000
|
|
Hi Charles
I would suggest using On Error Resume Next,
In the error routine write some code that will count for 5 seconds and then
try to upload again.
It would work very similar to your dial up networking when it encounters a
busy line when dialing up, it doesn't break down with an error because
there's an error handler in there to tell it to dial again after so many
seconds.
I Hope this helps
Kind Regards
Oliver Dempsey
----- Original Message -----
From: Charles <sel_rahc@h...>
To: ASP Databases <asp_databases@p...>
Sent: Tuesday, January 15, 2002 9:03 AM
Subject: [asp_databases] HELP! Update concurrency error handling???
> Hi!
>
> Im working on a web application that has heavy database usage by users.
> Unfortunately I am running into a few problems now :(
>
> My main problem is user concurrency in updating!
>
> For example, if 2 users attempt to add their email address in a table at
> the exact same time, one will go through while the other will recieve an
> error...
>
> How do you handle user update concurrency? I'm trying to figure out how to
> handle the error(s) thrown by more than one user attempting a table update
> at the same time.
>
> I was thinking some type of 'cue' code perhaps? How do the people that
> write programs used my many many users handle this problem?
>
> Any point in the right direction, or sample code would be VERY helpful!
>
> thank-you a TON!
>
> Sel
$subst('Email.Unsub').
>
>
|
|
|
View Cart
