kfenske
asked on
Send attachment without MAPI controls
I am doing this in Access 97. I am attempting to send and receive MAPI messages with attached files and cannot get SIMPLE MAPI go do it. I believe SIMPLE MAPI cannot. I have tried with the msmapi32.ocx control but cannot get this to distribute to the client PC so I have given up.
Is there any other method of using attachments in MAPI without the msmapi32.ocx control. Also, my cilents are using Exchange and not Outlook so I don't think Outlook Automation will work.
Thanks,
Ken
Bonus Question: How can I find out the default MAPI profile for a use so that I don't need to ask them the first time they use the application? It must be possible since forcing the profile dialog to appear has the default profile as the default selection in the dialog's combo box.
Thanks
Is there any other method of using attachments in MAPI without the msmapi32.ocx control. Also, my cilents are using Exchange and not Outlook so I don't think Outlook Automation will work.
Thanks,
Ken
Bonus Question: How can I find out the default MAPI profile for a use so that I don't need to ask them the first time they use the application? It must be possible since forcing the profile dialog to appear has the default profile as the default selection in the dialog's combo box.
Thanks
ASKER
I have two questions concerning your helpful answer:
1. Do you know if there might be a licensing issue I'm running into? I once got a message to that effect during testing but can't find any info on a file or registry entry to add for the license.
2. Thanks for the profile info, could you tell me how to read the registry from Access Basic?
Thanks,
Ken
1. Do you know if there might be a licensing issue I'm running into? I once got a message to that effect during testing but can't find any info on a file or registry entry to add for the license.
2. Thanks for the profile info, could you tell me how to read the registry from Access Basic?
Thanks,
Ken
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I think I figured out the problem with licensing. It seems that I had copied the mapisession and mapimessage objects from my VB app to the Access app. While this worked fine on my machine it did not work on the client. When I recreated the objects directly in Access it seems to have fixed the problem.
Thanks for the great answer on the registry!
Ken
Thanks for the great answer on the registry!
Ken
Regarding the OCX issue. I noticed that you made another post about difficulties that you are experiencing in distributing your application. Once you have resolved that problem, you will find that the msmapi32.ocx problem should go away.
There are alternatives to using msmapi. In addition to third-party controls (such as Quiksoft's EasyMail, et. al.), you can program directly to the MAPI API layer. However, I don't recommend it. It takes a lot of work, is not well documented, and I am not even sure if you can do it directly from Access. The OCX is there for a reason :)
You can determine the default MAPI profile by reading the registry.
In NT, this information is found at HKEY_CURRENT_USER\Software
In 95, it's at HKEY_CURRENT_USER\Software
Hope this helps!
zsi