>We intend to use wwipstuff to send mail from our db package.
>
>The sendMail works ok when the connection has been established properly ie:
>- permanent lan-based connection,
> or
>- dial-up modem connection has been successful.
>
>BUT if the dial-up connection has gone wrong (wrong pswd, physical issue), it will not prompt the connect "dial-up" connector again.
>
>The only way to fix it: close the VFP-based exe(or vfp session when debugging) and load it again.
>
>CLEAR ALL doesn't even solve it. Something seems to lock up somewhere. Any clue or simple alternative to wwipstuff?
I think that this is a problem internal to wininet- something internal is incorrectly flagged as connected, so no further attempt at connection is made.
Try this code before calling SendMail-
DECLARE INTEGER InternetAttemptConnect IN WinInet.dll Integer
llConnected = InternetAttemptConnect(0)=0
I have a fear that this function will incorrectly return 0 even if the computer is not connected, but if WinInet knows there is no connection, this will invoke one.
Erik Moore
Clientelligence