|
-
Mar 17th, 2001, 12:50 PM
#1
Thread Starter
Addicted Member
Hi,
Can someone help explain to me the unattended execution option? I have read about it, but I think I must be missing something.
It says this will allow my exe to run without user intervention. Does this mean it won't run if i call it from code without this option? Because I thought it would.
It says it allows the component to be multi-threaded, but then it says it doesn't effect the threading model. It says that VB only supports multi threading in components with this option. Huh? What's the real story?
It says it suppresses all form of user intervention, like msgbox, err, etc .... If I don't expose any type of user intervention does this effect me?
What are the advantages and disadvantages of this option?
Please! Any help would be greatly appreciated!
Thanks!
That which does not kill us, only makes us stronger. 
-
Mar 21st, 2001, 03:48 PM
#2
Hyperactive Member
Unattended execution allows all runtime errors to be written to the application event log instead of popping up with a message box.
Basically, the only threading supported is apartment threading so as long as your DLL is not single threaded, you won't have anything to worry about.
-
Mar 21st, 2001, 04:01 PM
#3
Thread Starter
Addicted Member
Thank you for the help. Lethal also explained this to me.
One last thing though...
If I raise an error in an active X exe will the error dialog be displayed on the client machine or the server machine?
Thanks!!
Last edited by wolfofthenorth; Mar 21st, 2001 at 05:43 PM.
That which does not kill us, only makes us stronger. 
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
|