How to open outlook attachments without downloading them

[Juvigy]

I think there was a setting in outlook security options where you can set not to get this msg. Options\trust center , Macro settings , Programmatic Access. You can also 'sign' your script with MS certificate , but that is more complicated solution.

[Bert]

just thinking outside the box - download it to a ram drive then when outlook closes, delete the ram drive. 

[Earthshine]

i had that thought but thought they would laugh at me like usual. lol 

ours is hosted in the cloud as is our office subscription. i don't think we can do the folder thing

Edited June 6, 2018 by Earthshine

[Bert]

Another option - sandiboxie

[Gowrisankar]

On 6/5/2018 at 7:36 PM, water said:

Another way is to use the first 4 parameters of _OL_Open to click away the message.

It works @water. Thank you.. I've slightly modified the "_OL_Warnings" to choose the "10 minute" delay option from the drop down.

[Gowrisankar]

@water When I used the UDF, once I got the error 9  from "_OL_Open", which means "No profile has been configured or there is no default profile for Outlook". But I found that there are profiles configured already. Can you please help to resolve this? Sometimes this error resolves the next day. I am not sure what is wrong. 

[water]

Can you please post your _OL_Open statement?

[Gowrisankar]

23 hours ago, water said:

Can you please post your _OL_Open statement?

Global $oOutlook = _OL_Open(True, @ScriptDir & "\_OL_Warnings.exe", 3000, 2000)

Edited June 27, 2018 by Gowrisankar

[water]

Nothing wrong with the Open statement. Does this always happen or only in rare cases?

[Gowrisankar]

It happens sometime @water. Not always. That is why I am unable to identify the reason.

[Gowrisankar]

The outlook application is opened from Citrix environment. Similarly the code is executed from Citrix environment. Could it be the reason?

[water]

Maybe. At the moment I see no other cause for such an error.
Outlook and the AutoIt script need to run on the same machine under the same user id.

[Gowrisankar]

2 minutes ago, water said:

Maybe. At the moment I see no other cause for such an error.
Outlook and the AutoIt script need to run on the same machine under the same user id.

The user id is same for Outlook and the script. The script tries to access a shared mail box that is configured in the outlook along with individual email address.

[water]

5 hours ago, Gowrisankar said:

It happens sometime

That's why I'm unable to identify the reason as well
A missing profile tells us that Outlook hasn't been configured as needed. In this case _OL_Open should always return @error = 9 or never.

You are sure that the environment doesn't change between runs of the script? When you connect to the Citrix environment do you always get connected to the same machin with Outlook installed properly?

[Gowrisankar]

7 hours ago, water said:

You are sure that the environment doesn't change between runs of the script? When you connect to the Citrix environment do you always get connected to the same machin with Outlook installed properly?

@water The environment doesn't change between scripts executions. We are not connecting to any machine from Citrix. Outlook is available as an application in Citrix itself. The back-end is a server which hosts these applications and provides disk space for the files.

[Gowrisankar]

I almost got the issue. 

My code manipulates Outlook, Mainframe and Excel applications. It appears that Outlook and Mainframe are hosted in different servers. That is why the code which is placed in the Mainframe server location, doesn't establish connection with Outlook. When I try running from the Outlook server location, the code doesn't establish connection with Mainframe. But all these folders are accessible from Citrix dashboard. Is there anyway to fix this?

The reason it worked fine sometimes should be that it was executed from Outlook server location.

[water]

I see.
All client applications accessed by the script need to be installed on the server where the script runs.

[Gowrisankar]

A friend of mine suggested an idea. It actually works.

1. Open the Mainframe server location. Close existing Outlook application.

2. Write a script there with Run("C:\Program Files (x86)\Microsoft Office\Office15\OUTLOOK.EXE") and execute.

3. Then execute the entire macro. 

Now connection with Outlook and Mainframe are both established.

[water]

Great your problem could be solved

[Gowrisankar]

Thanks @water. Will need your guidance in future too.