|
-
Oct 4th, 2000, 02:51 PM
#1
Thread Starter
New Member
I have ASP code which includes a function that will call a component in an MTS package via Server.CreateObject. The component in the MTS package has the transaction attributes set to "Does not support transactions". Would you still need to use the declaring and setting of the object context within this component(dim objctx as objectcontext and set objctx=GetobjectContext) if not supporting transactions? I didn't think so since there aren't any transactions or need to use SetAbort or SetComplete but I could be wrong.
Now, if I have a second module that uses the statement:
Dim loADSI As New Module1.Component to access the above component in the MTS package: Would it be necessary for both of them to be in the MTS package? Would it at least be necessary to change the 'As New' code in this second module to using 'CreateInstance'?
I would appreciate any information anyone can provide...
Thanks!
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|