|
 |
asp_components thread: Database updates getting rolled back on ASP page
Message #1 by "Reza Mubeen" <rezamubeen@n...> on Sat, 8 Mar 2003 13:33:46 -0600
|
|
I have a web application hosted on IIS5 and COM+ components making up the
middle tier. I do have too much experience working with the object context
on ASP. Another thing to note is all my COM+ components are made up of
collection classes and their respective members. A particular object User
has access to objects such as contact,company etc. On most pages with the
user object I have had to add 'transaction=required' (dont know why this was
just guess work) but they worked better with this else the object would just
hold up the page trying to do the updates on that object. I have finally
come to a page which is very much like a registration page. I am having
similar problems onthis page too. The hang up problem got solved by adding
the 'transaction=required' statement. But kow it seems like the transaction
for some reason gets rolled back by the end though no visible errors occur.
I checked the values form the database after the update and the values are
their but i think they get rolled back because by the end of the asp script
the database tables themselves are empty. Could any one help me out. Do I
need to add setabort or setcomplete somewhere on the asp page.
Thank you in advance
|
|
 |