So the user knows the name of the SMTP (pop) server and the user is aware and can enter their IP address. The reason I ask is that the DLL solution needs the SMTP Server name and the IP address.
I packaged it - and I need to write a littel DBF with emails in it to test the cycling.
>I found that the problem is in line
>
>
nWait = WSAWaitForMultipleEvents(1, @hEventRead,;
> 0, 1000, 0)
I cannot recall this in the DLL - but there may be some messaging delay - but if you add it up it only eats about 8 or 9 minutes for 500 mails - so something else might be clogging it.
I will get the DLL demo to you later - but understand - a SMTP server name and a IP address will be required to use it.
>>You do have an STMP server on your desktop, right?
>
>No. I use my ISP SMTP server.
I think this is always the case - I just wondered wher or how you found the name - the CDO object was an examlpe of one container that has the SMTP server name. There are otherways to get it - but as long as you have the SMTP name and IP to feed the DLL model - then everything should be okay.
>2.
http://www.sweetpotatosoftware.com/SPSBlog/PermaLink,guid,40a6327a-44f7-4e98-9e83-cb50c2ebd4c1.aspxSweetpotato does some pretty cool stuff!
>
>wrote that it is not included with newer OSes.
>
>3.
http://fox.wikis.com/wc.dll?Wiki~CdoEmail>wrote that CDO requires Windows server or Outlook Express.
I have a CDO object - but I don't have outlook - I think it's part of the XP OS.
>
>Direct mail sending from VFP works in all environments. So I think I must use it.
It will work as long as it can be fed a SMTP server name and IP - I'll have a "sketch" in you mailbox in a while! I am interested in seeing if it really works - I was using it for one shot emails - but the app instatnced the object at the top.
Imagination is more important than knowledge