>>>>>>What I believe is that your code is running but faces a bug probably because of the authorization to execute the task. So, it stops processing. I believe your timer is well setted up. I would trace the code to see until which line it gets executed.
>>>>>

---

>>>>>Michael,
>>>>>Very astute! I was just taking a break and had this revelation. I am guessing that when using a System Account the file is not found on the network (because no network access) and therefore the processing method is not run.
>>>>>
>>>>>But, like you said, there must be some kind of bug that pops up when running as a service and it therefore trys to interact with the desktop and just hangs.
>>>>
>>>>Well, those type of apps that run as a service, are often using timers. We run as well some. Those little things to set up are to be taken with care. It usually mostly relates to the account being used to run the application.
>>>>
>>>>Let us know about your result. It's always interesting to know what is causing those type of behavior.

---

If you end up having to run the service using the System Account, then you could enable network access (under a different account) using

DWORD WNetAddConnection2(
>>>  LPNETRESOURCE lpNetResource,  // connection details
>>>  LPCTSTR lpPassword,           // password
>>>  LPCTSTR lpUsername,           // user name
>>>  DWORD dwFlags                 // connection options
>>>);

Let me know if you need to resort to this and would like help with the DECLARE and call.
>>
>>Houston,
>>
>>Thanks for posting this. I'm interested in seeing how George deals with this as I need to create some VFP-based services as well.
>

>He's not dealing with it well! He's heading straight for the liquor cabinet! LOL
>

George,

Well, I don't drink but I'm sorely tempted after the last couple of weeks... <g>