also remember that outlook may spawn an instance of msword, if outlook is configured to use word as it's email editor. Which may be controlled by corporate domain policy...etc
-----Original Message----- From: Discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] Behalf Of Steve Johnson Sent: Monday, April 02, 2007 9:05 AM To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM Subject: Re: [ADVANCED-DOTNET] UnauthorizedAccessException when instantiating Word On 4/2/07, Jason Nah <[EMAIL PROTECTED]> wrote: > > The thing that's exteremely confusing is that it happens only > sometimes!.... > So yes sometimes it works... other times... it doesn't! > > I'm starting to find this happens to be an extemely common thing with M$ > technologies!!!!! > Jason...MS technologies work when the developer knows what he/she is doing. Read up on dcomcnfg and the difference between launch and access permissions. I'll bet you a dollar that when it magically "works" it is because an instance of Word is running in the current user's logon session. I'll also bet a dollar that when it's mysteriously "busted" it is because Word is not running. The problem is likely that the user has access permissions, but not launch permissions. If this is not the problem, then I'm sure that we can find another perfectly logical explanation. Software does not auto-mutate. When it does not work, it is because there is some environmental or data configuration it does not "like". BTW, M$ is something that idiots and kiddies say. If you want to be treated like a pro, then act like one. -- Steve Johnson =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
