On 4/2/07, Jason Nah <[EMAIL PROTECTED]> wrote:
Upon reading your comments.... just for clarification... 1. A word instance was already running (as in I had an open Word instance) 2. In that same session, the COM interop bridge was able to create a new word instance and also fail with the above error (hence the confusion). So it doesn't appear to fall into permissions for launching and access. I'll dig around and see what happens...
Hmm...I've done a veritable ton of MS Word automation and every time I've seen this problem, it's been launch/access perm configurations. I guess I owe you two dollars, though :) I still think you ought to examine the permissions in dcomcnfg. It may not fall into the exact scenario I'm thinking of, but you should check it out anyway. -- Steve Johnson =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
