Since you are using FTP already, and are looking for backup solution,... one other option not discussed yet.

using windows sharing, where as you have one server setup with a shared drive on the internet, for dropping files. windows or Linux ..

If it turns out that email is the way to go, you might think about using blat or blat.dll, or something else like that, which does not require mapi to be configured. that way, you have more control of how email is being sent. I cant tell you how often I have taken calls from users telling me that they child changed their email settings, or they downlaoded netscape set it as their default email, but... didnt configure it.

Using your application to control the flow, and communication with the smtp client as much as possible will help you sleep nights. knowing that at at least if your code is good, and the smtp server they are connected to is good, it should work.

Add into it other controls like ole - outlook , mapi, while adding features, also brings into the picture new levels of complexity - users - login to the machine, Profiles , what email client and so on. most of which you really have little or no control of.. since they are port of the desktop, and or other software..

Bob Lee



>Thanks Bob
>
>Your comments on FTP are all valid:) which is why its the primary method we will be using for the distribution of these files. The Email system is only being used as a backup system because we have to provide more than one internet mechanism for the transfer. Our other fallback system involves motorcycle couriers and floppy disks:)