ASP 3 transactions and SSI

[Anders]

Using the ASP 3 transaction functionality requires that the transaction flag
is set as the very first code row, I understand. I now have a requirement to
implement a transaction in one of the pages. Unfortunately the whole site is
based on SSI (server side includes) that are being picked up based on the
users preferences. I have an index.asp page that does this selection, which
is always loaded first. Is there any way around this, or do you guys have any
other suggestions?

Thanks alot!

Anders

[Mike Brind]

Anders wrote:

Using the ASP 3 transaction functionality requires that the transaction flag
is set as the very first code row, I understand. I now have a requirement to
implement a transaction in one of the pages. Unfortunately the whole site is
based on SSI (server side includes) that are being picked up based on the
users preferences. I have an index.asp page that does this selection, which
is always loaded first. Is there any way around this, or do you guys have any
other suggestions?

I didn't know ASP had any "transaction functionality". Can you give an
example of how this works?

--
Mike Brind

[Anthony Jones]

"Mike Brind" <pa*******@hotmail.comwrote in message
news:11*********************@i42g2000cwa.googlegro ups.com...

>
Anders wrote:

Using the ASP 3 transaction functionality requires that the transaction

flag

is set as the very first code row, I understand. I now have a

requirement to

implement a transaction in one of the pages. Unfortunately the whole

site is

based on SSI (server side includes) that are being picked up based on

the

users preferences. I have an index.asp page that does this selection,

which

is always loaded first. Is there any way around this, or do you guys

have any

other suggestions?

I didn't know ASP had any "transaction functionality". Can you give an
example of how this works?

See:-

http://msdn.microsoft.com/library/en...8d16ca7465.asp

Basically you can mark an ASP script as requiring a transaction then use ADO
or (COM+ objects marked for transactions) to update multiple distributed
data sources. As long as all providers support two-phase distributed
transactions the whole set of changes can be commited or rolled back as a
single transaction.

Anthony

--
Mike Brind

[Mike Brind]

Anthony Jones wrote:

"Mike Brind" <pa*******@hotmail.comwrote in message
news:11*********************@i42g2000cwa.googlegro ups.com...

Anders wrote:

Using the ASP 3 transaction functionality requires that the transaction

flag

is set as the very first code row, I understand. I now have a

requirement to

implement a transaction in one of the pages. Unfortunately the whole

site is

based on SSI (server side includes) that are being picked up based on

the

users preferences. I have an index.asp page that does this selection,

which

is always loaded first. Is there any way around this, or do you guys

have any

other suggestions?
>

I didn't know ASP had any "transaction functionality". Can you give an
example of how this works?

See:-

http://msdn.microsoft.com/library/en...8d16ca7465.asp

Basically you can mark an ASP script as requiring a transaction then use ADO
or (COM+ objects marked for transactions) to update multiple distributed
data sources. As long as all providers support two-phase distributed
transactions the whole set of changes can be commited or rolled back as a
single transaction.

Now I remember. I even seem to recall that there's a chapter on it in
one of my books.... Clearly I never studied it in any real detail, have
never used it and forgot all about it.

--
Mike Brind