I'm setting up a site that prompts a user for information
about people and stores the results in a Access database.
This database is then used to create accounts on the
network.

To store the user data I need to run three separate INSERT
queries into an Access 2000 database.

What I'd like to know is, should one of these updates
fail. What should I do? Especially if its the second or
third update! At the moment all I'm doing is watching to
see if there is an error in each update function. If
there is one, then it abandons the whole thing and
redirects to an error page.

Should I be trying to backout of any previous updates, or
trying the broken function... or something else? What is
the correct course of action in such circumstances?

TIA,

Colin

use transactions - ADO supports them with ease. if one fails, the rest
will be rolled back, and they're also well documented.





________________________________________
Atrax. MVP, IIS
http://rtfm.atrax.co.uk/

newsflash : Atrax.Richedit 1.0 now released.
http://rtfm.atrax.co.uk/infinitemonk...trax.RichEdit/

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

Atrax <atrax@dontspamatrax.co.uk> wrote in message news:<e3SbHHunDHA.1948@TK2MSFTNGP12.phx.gbl>...[color=blue]
> use transactions - ADO supports them with ease. if one fails, the rest
> will be rolled back, and they're also well documented.[/color]

ADO can do that! Excellent, I wasn't aware of this feature. I'll
crack open my ASP book tomorrow and look it up, I'm sure it has a
section on ADO.

Thanks very much!

Colin