Here is a piece of the helptext of an app I wrote. Just to let you know one POV.

ClickWork does not send an e-mail directly. Instead, it prepares a text for the e-mail and then starts your e-mail client . It is up to you whether or not you actually send the e-mail. The advantage of this route is that you have the e-mail in your regular e-mail database.

ClickWork might paste a text directly into the body, but there is a limitation to the size of the body-text that can be pasted directly. The amount of text that ClickWork wants to add is quite large, especcially if it includes technical info. In fact, it can be larger than some e-mail clients can handle if done programmatically. In the old days, the technical info could have been added by way of an attachment, at least in some e-mail clients, most notably MS Outlook. However, virusmakers have made frequent use of such doors and even Microsoft decided that this door had to be closed. They have done so with service packs and adding an attachment programmatically is no longer possible.

The decision was made to put the whole text, including the eventual technical info, into the clipboard and to ask the user to paste it into the body of the e-mail. The additional advantage is that your signature will now indeed be included also (which would else not have happened).


>Hi,
>
>I have a client running a VFP6 app on a Novell network. They want to be able to select clients from the VFP app and send them email with attachments. These email addresses are in the VFP database. They use Groupwise for their email.
>They do not want these email addresses in Groupwise.
>
>They have the client selection form already in place for other purposes and now would like to use it to send email. I have used SMTPWizard successfully at other sites but they did not use Groupwise.
>
>Any suggestions as to the best approach to this problem? Can I avoid Groupwise or is it best to work with it if possible?
>
>Thanks
>
>Barb