What about a dll? That doesn't have a UI Al -----Original Message-----
I would agree with Ted. Visual FoxPro is not the best choice for a service EXE as it is hard to make one that doesn't present any UI, and you can't build one natively. Also if there is scheduling involved then you are re-inventing the scheduling wheel too. .NET can create services easily, however for any sort of complex scheduling you're looking at a library called Quartz.NET. As Ted says, do a VFP exe that does what you want once, then exits. Then use the power of the Windows scheduler to run it as needed. There is no real need for this to be a service, or TSR as they used to be called in the olden days. _______________________________________________ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/001201d0d40b$fca169f0$f5e43dd0$@com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.