On the same topic:

I have a nice piece of working code that runs on the command line and does exactly what I need. However when I put this into
the task scheduler on our windows 2012 server it just hangs. My theory is that the first time you use the ODBC, if it does not
find the eztask or currency files it will do a popup dialog window to ask you to point to where these are. Something I had to
do when it ran the first time on the command line.

I believe that our problem is that the ADSPROF.LD4 file that we have points to a network drive that is mounted on the server
and it does not like that. I have had to change the values to point to the non-network drive. We use the network drive on the server
to keep the file systems correct for the clients as well.

So, my question is. Has anyone been able to use the ODBC driver in code that runs on the task scheduler? If so how did you do
it? Is there a way to pass the file values for the EZTASK and Currency Files to the ODBC driver in code? So something in the connection
string. If so what are the keywords to send?

Thanks!
Brian

I suspect the issue is "drive mappings".
To run under a schedule task you need to use UNC drive mappings everywhere including ADSPROF.??? in the data folder.

The path to EZTASK and Currency Files comes from the above mentioned ADSPROF.??? and should use UNC not drive letters.

Thanks for the reply Michael!

I tried that... no luck. Works on the command line but not in the task scheduler.

is the ODBC driver pointing to the database using the UNC path as well?

Yes, it does now. It did not.... however still no luck.

Disconnect the drive mapping and run the command line.

I now have enough feedback in the program to know that when it is run in the task scheduler it hangs while trying
to get the connection to the ODBC driver. It hangs there and will hang forever. So now I am pretty sure it is
the ADSPROF.??? file that is causing it to hang.

One of the things that I have found is that the ADSPROF.??? gets over written and the pointers change... I assume
it is because the clients are using the mounted drive notation.... is that right?

Thanks!
Brian

Thank You Patricia!!!

I disconnected the drive then ran the script on the command line. This gave me the popup dialog for the task and currency files. I
put in the UNC label for the directories and it started the command. Killing the script and cleaning up the files, I tried running it via
the task scheduler and it is running as it is suppose to.

Thank you again!

Cheers,
Brian