Can Access support ASP transactions?

[David Bray]

I have an Access database on an ISP's web-space which is accessed
through ASP - all standard stuff.

Can anyone tell me whether ASP's object.context methods for
transactions will work with Access? My ASP reference talks about SQL
Server and XA protocol databases but I have no idea as to whether
Access is covered by the latter.

Thanks

[TC]

You'd be talking about Jet - not Access. Access is just the UI stuff (forms,
reports etc.). Jet is the underlying database engine. Jet does have
transactions, but I don't know whether they work from ASP.

Googling on:

"xa protocol" jet

lead immediately to a humungous Active Server Pages Guide. Perhaps the
answer is in there somewhere.

HTH,
TC
"David Bray" <dj****@btinternet.com> wrote in message
news:4a**************************@posting.google.c om...

I have an Access database on an ISP's web-space which is accessed
through ASP - all standard stuff.

Can anyone tell me whether ASP's object.context methods for
transactions will work with Access? My ASP reference talks about SQL
Server and XA protocol databases but I have no idea as to whether
Access is covered by the latter.

Thanks

[MeadeR]

MS Access does not support the transaction type process - such as
transaction begin, etc. - T-SQL (MS SQL) does since MS SQL - SQL is
procedural based where Access uses a much simpler model

dj****@btinternet.com (David Bray) wrote in message news:<4a**************************@posting.google. com>...

I have an Access database on an ISP's web-space which is accessed
through ASP - all standard stuff.

Can anyone tell me whether ASP's object.context methods for
transactions will work with Access? My ASP reference talks about SQL
Server and XA protocol databases but I have no idea as to whether
Access is covered by the latter.

Thanks

[TC]

Not true. MS Jet (the default database engine used by Access) has
BeginTrans, Commit & Rollback methods; check online help.

TC
"MeadeR" <Me****@ComputerSOSNJ.com> wrote in message
news:32************************@posting.google.com ...

MS Access does not support the transaction type process - such as
transaction begin, etc. - T-SQL (MS SQL) does since MS SQL - SQL is
procedural based where Access uses a much simpler model

dj****@btinternet.com (David Bray) wrote in message

news:<4a**************************@posting.google. com>...

I have an Access database on an ISP's web-space which is accessed
through ASP - all standard stuff.

Can anyone tell me whether ASP's object.context methods for
transactions will work with Access? My ASP reference talks about SQL
Server and XA protocol databases but I have no idea as to whether
Access is covered by the latter.

Thanks

[Tom van Stiphout]

On 27 Oct 2003 14:30:23 -0800, dj****@btinternet.com (David Bray)
wrote:

I think you're on the wrong track. Object Context is used where COM
objects vote if the overall transaction (and this term is used loosely
here) can continue or not. So you could write an object method that
interacts with an Access database, decides it doesn't like the
results, and calls SetAbort.

Access (or better: Jet) is not a COM object in the sense used above.
However, it does support database transactions (and this term is used
strictly here: BeginTrans, CommitTrans, Rollback), which then could be
used to decide circumstances are not good and SetAbort should be
called. In pseudocode:
on error goto errorhandler
BeginTrans
'credit one account
'debit another account
CommitTrans
ObjectContext.SetComplete
Exit Sub
errorhandler:
Rollback
ObjectContext.SetAbort
Exit sub

Hope the difference makes sense to you.

-Tom.

I have an Access database on an ISP's web-space which is accessed
through ASP - all standard stuff.

Can anyone tell me whether ASP's object.context methods for
transactions will work with Access? My ASP reference talks about SQL
Server and XA protocol databases but I have no idea as to whether
Access is covered by the latter.

Thanks

[Lyle Fairfield]

dj****@btinternet.com (David Bray) wrote in
news:4a**************************@posting.google.c om:

I have an Access database on an ISP's web-space which is accessed
through ASP - all standard stuff.

Can anyone tell me whether ASP's object.context methods for
transactions will work with Access? My ASP reference talks about SQL
Server and XA protocol databases but I have no idea as to whether
Access is covered by the latter.

TTBOMK ASP has no direct connection with databases whatsoever. Typically
ASP uses ADO and an OLEDB provider to access databases such as MS-SQL or
MS-Jet (I suppose one might call JET, "the native provider for MS-Access").
If the provider supports transactions, then ADO and OLEDB can use

BeginTrans
CommitTrans
and
RollbackTrans

as methods of the connection object.

Of course, Jet and MS-SQL may also have their own internal transaction
handling. From MS-SQL help:
**** begin quote ****
If a severe error prevents the successful completion of a transaction, SQL
Server automatically rolls back the transaction and frees all resources
held by the transaction.
**** end quote ****

If you are messing with databases through ASP-ADO then you really should
read the pertinent parts of ADO help and MS-SQL Books on Line. Sometimes
people with a background in Access do not realize that MS-SQL and ADO are
so powerful and extensive that working with either could be a full time
job. They are immense subjects and learning everything about them is
challenging. There are no simple answers in working with these
technologies; we may be lulled into thinking that there are because Access
has a history of making things easy for us. But when we leave Access, (and
ASP has zip to do with Access) we must learn our trade.

--
Lyle
(for e-mail refer to http://ffdba.com/contacts.htm)

[MeadeR]

Tom - my confusion - Access (Jet) does not support Transactions
imbedded inside the SQL as T-SQL does (MS SQL) - but via Access VB you
can simulate this. So what I would consider native transaction
processing is not supported inside of Access (Jet) SQL...(correct?)
Tom van Stiphout <to*****@no.spam.cox.net> wrote in message news:<mk********************************@4ax.com>. ..

On 27 Oct 2003 14:30:23 -0800, dj****@btinternet.com (David Bray)
wrote:

I think you're on the wrong track. Object Context is used where COM
objects vote if the overall transaction (and this term is used loosely
here) can continue or not. So you could write an object method that
interacts with an Access database, decides it doesn't like the
results, and calls SetAbort.

Access (or better: Jet) is not a COM object in the sense used above.
However, it does support database transactions (and this term is used
strictly here: BeginTrans, CommitTrans, Rollback), which then could be
used to decide circumstances are not good and SetAbort should be
called. In pseudocode:
on error goto errorhandler
BeginTrans
'credit one account
'debit another account
CommitTrans
ObjectContext.SetComplete
Exit Sub
errorhandler:
Rollback
ObjectContext.SetAbort
Exit sub

Hope the difference makes sense to you.

-Tom.

I have an Access database on an ISP's web-space which is accessed
through ASP - all standard stuff.

Can anyone tell me whether ASP's object.context methods for
transactions will work with Access? My ASP reference talks about SQL
Server and XA protocol databases but I have no idea as to whether
Access is covered by the latter.

Thanks

[Tom van Stiphout]

On 28 Oct 2003 03:26:50 -0800, Me****@ComputerSOSNJ.com (MeadeR)
wrote:

Lyle explains it well. Indeed you don't have stored procedures in
Jet, no multi-statement queries whatsoever. You interact with Jet
through one of the providers. From ASP, you would typically use ADO.
Doing so, you can use ADO's transaction support and write code similar
to my example.

-Tom.

Tom - my confusion - Access (Jet) does not support Transactions
imbedded inside the SQL as T-SQL does (MS SQL) - but via Access VB you
can simulate this. So what I would consider native transaction
processing is not supported inside of Access (Jet) SQL...(correct?)
Tom van Stiphout <to*****@no.spam.cox.net> wrote in message news:<mk********************************@4ax.com>. ..

On 27 Oct 2003 14:30:23 -0800, dj****@btinternet.com (David Bray)
wrote:

I think you're on the wrong track. Object Context is used where COM
objects vote if the overall transaction (and this term is used loosely
here) can continue or not. So you could write an object method that
interacts with an Access database, decides it doesn't like the
results, and calls SetAbort.

Access (or better: Jet) is not a COM object in the sense used above.
However, it does support database transactions (and this term is used
strictly here: BeginTrans, CommitTrans, Rollback), which then could be
used to decide circumstances are not good and SetAbort should be
called. In pseudocode:
on error goto errorhandler
BeginTrans
'credit one account
'debit another account
CommitTrans
ObjectContext.SetComplete
Exit Sub
errorhandler:
Rollback
ObjectContext.SetAbort
Exit sub

Hope the difference makes sense to you.

-Tom.

>I have an Access database on an ISP's web-space which is accessed
>through ASP - all standard stuff.
>
>Can anyone tell me whether ASP's object.context methods for
>transactions will work with Access? My ASP reference talks about SQL
>Server and XA protocol databases but I have no idea as to whether
>Access is covered by the latter.
>
>Thanks

[David Bray]

Just to say thanks for the replies. Lyle's and Tom's comments helped
to remove the (temporary) blinkers! Its ADO I'm using to access the
database inside my ASP code and so its there I should be looking.

Thanks!