Sending Email Dependent on Default Email Client

Truth be told if you want it for any mail client I'm not sure how trivial it will be.

Adding the attachment to the mail item is the tricky part given the code will vary by mail client ... if you sent only the link to the attachment it might be viable via a mailto url.

Maybe some of the other guys will have some ready made code available...

Having re-read your post perhaps you're concerned only with two clients - namely Outlook and Lotus Notes... in which case you might find you can determine the client and act accordingly - perhaps along the lines of:

Please Login or Register  to view this content.

obviously the MsgBox items would be replaced with calls to appropriate routines.

Whether you would need to use late binding for your code I don't know ?
(ie would Lotus client debug if using early binding with OL library or is OL library available by standard with Office irrespective of client installation)

There are plenty here with Lotus experience who can offer more insight I'm sure.

Not sure if this earlier post, see Leith's code, will help. maybo, you could use CDO

I'm not sure CDO would allow you to display the mail item (as opposed to send)

Outlook has a .Display method you can use instead of .Send

not sure about Lotus notes.

Andy, to sate my curiosity...

Do you know if the OL library will be available irrespective of the installed mail client if any other Office apps are installed ?
By that I mean: if I ran Lotus Notus but had MS Excel installed would the OL library be available ?
(just trying to ascertain for future ref. if code dependent upon early binding would compile on say a Lotus client)

edit: for the record I'm neither advocating nor dismissing early binding - just curious

I could not say for certain. But I would image that if your email client was Lotus Notes you, or the IT. dept, would not bother installing Outlook. So the library would probably not be available.

Thanks Andy.

Julesdude, based on the above I'd say that if you do opt for an either/or routine you should avoid being reliant on Early Binding on the Outlook side of things.

The general principles of Early vs Late Binding in VBA are outlined here: http://word.mvps.org/faqs/interdev/e...atebinding.htm

If you have referenced the Outlook Library explicitly (VBE -> Tools -> References) then the chances are you're using Early Binding in your Outlook code.
The problem with Early Binding is when you distribute the file to a client PC which does not have the library you referenced available to it - it will be listed as :MISSING and will cause "issues".

Late Binding is slower to execute than Early Binding, however, the code should not generate any "issues" even if OL is not installed on the client (this assumes that the OL code is not invoked on a machine running Lotus Notes).

Other alternatives (to maintain Early Binding) would be to add/remove the appropriate OL Library upon the workbook Opening / Closing (where mail client is OL).
This too assumes the OL code is never invoked on a Lotus client.

To be clear though - most would opt for late binding where there is the potential for missing libraries across client PCs.

I hope that makes some sense ?