Hi Sergey,

thanks for the advice. Though, after applying it, I still get the error on oMessage = oOutlook.CreateItem(olMailItem).

The advice was to create NameSpace (oNameSpace = oOutlook.GetNameSpace("MAPI")
) after initializing Outlook object. The NameSpace gets created, TYPE('oNameSpace')='O' after.


>Hi Sasha,
>
>Take a look at Message #398853.
>
>>After this line:
>>
>>oOutlook = CREATEOBJECT("Outlook.Application")),
>>
>>I'm getting
>>
>>

>>WAIT WINDOW VARTYPE(oOutlook)                         - O
>>WAIT WINDOW TYPE('oOutlook.Name')+'-'+oOutlook.Name   - O-Outlook
>>

>>
>>Like I said, if Outlook was running already, everything's fine. Everything's happening on my machine, where I'm Administrator.
>>
>>Maybe some security setting in Exchange/Outlook?
>>
>>There is an Exchange server in the domain, but mail client is Outlook2000.
>>
>>(My machine is Win2000 SP2,VFP7,Outlook2000)
>>
>>Sasha
>>
>>
>>
>>>>I'm creating an Outlook object (oOutlook = CREATEOBJECT("Outlook.Application")) and immediately after a message object (oMessage=oOutlook.CreateItem(0)).
>>>>
>>>>If Outlook isn't running before these two statements, an error pops up: #1429 on *second* line with message:
>>>>'OLE IDispatch exception code 61704 from Microsoft Outlook: Internal application error'.
>>>>
>>>>If Outlook is running beforehand, everything's perfect.
>>>>
>>>>I tried with putting a 5 and 10 seconds pause in between these two statements to no avail.
>>>>
>>>>Have anybody seen this?
>>>
>>>DO you test to make sure the CreateObject worked? Do you use vartype() to check the oOutlook object? You could also use type() to check a property of the object (like Name) to make sure it is of type character.
>>>
>>>It sounds like Outlook isn't being instantiated at all.