I actually logged in to provide an update on this problem and saw your message. We have bypassed the problem by putting the application on a different machine. However, any insight you can offer will be appreciated since I may not have that option in the future.

I don't think>/i> we're dealing with a network drive, but I don't really know. All the other temp files which get created - ususally via SQLEXEC() against a MySQL database are created properly. It is only the file being created in

**wwipstuff.sendmail()
DECLARE integer SendMail ;
   IN (THIS.cDLLPath) ;

etc.

that presents a problem. I don't know what path that DLL is using.

There is another piece that has our network guy in tears (well....you know what I mean).

If I log into the workstation via Remote Desktop Connection and run the software it works just fine. If I log into the workstation with something that puts me directly in the workstation's active session (we use VNC for this) the EXE fails with the errors I'm describing. In both cases the same login ID and password is used. I've checked and the drive mappings are identical.

We have even tried the debugging trick of last resort - power the workstation off and on - to no avail.

Any insight on configuration differences will be appreciated by both me and the network admin.

Many thanks for any time you (or anybody else) can spend (and have spent) on this.


.......Rich

>Hi Rich,
>
>If you're dealing with a network drive you probably don't have permissions on the remote drive. Task Scheduler lets you configure the user account that the app runs under. I can't remember but I believe the default is SYSTEM which will not have remote access rights. Try changing the account to an account that does and the problem should go away.
>
>+++ Rick ---
>
>>We have a system which uses WWIPStuff to programatically generate emails. The emails are allowed to, but are not required to have attachments.
>>
>>The program is started each morning by the Task Manager and runs continually through the day. It uses a timer to check if there are any jobs to be processed. It has been working successfully for quite some time. We now have a problem.
>>
>>If the EXE is called manually (dbl-click in Explorer for example) everything runs correctly.
>>
>>However, when started by the Windows Task Scheduler, emails without attachements are processed correctly. The program has suddenly stopped sending emails which have attachments. The error message in the SendMail method of WWIPStuff is
>>
>>Couldn't create temp file for encoding x:\sendemail\rlp.txt
>>
>>The attachments are usually on a network drive. I've copied them into the directory where the program runs, but that did not have any effect.
>>
>>This program works just fine when initiated from Windows Explorer. It is only when called from the Task Scheduler that there are problems.
>>
>>Any insight will be greatly appreciated.
>>
>>Thanks to all............Rich