Re: Transactions and sub Procedures
- From: "Michel Walsh" <vanderghast@VirusAreFunnierThanSpam>
- Date: Fri, 22 Apr 2005 16:22:49 -0400
Hi,
In a complex transaction, where many components are involved, like
database AND objects in memory, a possible solution is to use some kind of
transaction manager that will commit or rollback each components
appropriately. COM+ has such transaction manager, but that is probably an
overkill. If all the modifications occur in a single database, use the SAME
database object if you want to include all the modifications in the
transaction. You have to organize your database object scope of existence
appropriately, and that SHOULD be a piece of cake.
Hoping it may help,
Vanderghast, Access MVP
"Diarmuid" <diarmuid@xxxxxxxxxxxx> wrote in message
news:%23SJyBCaRFHA.3104@xxxxxxxxxxxxxxxxxxxxxxx
> Ok, I want to set up a DAO transaction, which I have in my main procedure.
> But if I call sub procedures, any updates there won't be included in the
> transaction. I'd like to include the sub procedures, as I may need to
> rollback the whole lot.
> And advice on how I would do this?
> Thanks
> Diarmuid
>
.
- References:
- Transactions and sub Procedures
- From: Diarmuid
- Transactions and sub Procedures
- Prev by Date: Re: Accessing a Menu Item thru a Command button
- Next by Date: Re: Run-time error '2424'
- Previous by thread: Transactions and sub Procedures
- Next by thread: Setting RecordSource on Subform
- Index(es):
Relevant Pages
|
