A similar effect could be had with a mostly inactive loaded program with activeX/OLE linking&emebdding hooks,
which are called by the XMLdropper and restarted if/when the program for some reason has crashed.

On todays HW probably not a big difference in perf or other interesting measure, as long as sequential XML processing
is guaranteed by external factors in advance. Otherwise some poolmanager logic is needed -
go for the poolmanager example in vfp(6?) which later was shuffled around.
Easy enough to grok and able to work most such scenarios -
guessing that external read spead is a more limiting factor here on my part.




>Thank you. I believe I did see this post a long time ago. But never actually built a service. I will check it out again.
>
>>There is a way make a your app.exe a windows service. The service can be setup to restart your app if it crashes or quits responding. Someone reboots the computer, the service automatically starts again. Take a look at Calvin's blog. http://blogs.msdn.com/b/calvin_hsia/archive/2004/12/13/282351.aspx
>>
>>>I need to process an XML file(s) sent by an external application. I can make the external application drop the XML files in a folder and have a VFP with a timer to pick up these files. Or I can make the external program to automatically run a VFP application and pass it the name of the XML. The latter approach has advantage over the timer program: the timer program could crash and need to be restarted.
>>>
>>>>Why does the app need to start so often? It sounds like there is a better solution.
>>>>
>>>>>Hi,
>>>>>
>>>>>If a process external to VFP application starts a VFP exe application frequently (say every minute or even every half a minute), then lets VFP app process some day and then closes it, is there a potential problem with this scenario?
>>>>>
>>>>>TIA