Nick Cipollina wrote: >> Write a small simple VFP program that utilitizes the VFP timer, and then >> turn it off while in your processing routine (when the flag condition is >> met), then turn it back on as you exit the processing routine. What's >> wrong with that idea? Is this one of those "if it sounds too good to be >> true, ..." kind of scenarios? >> > > > We have an app that essentially does this, except we don't turn the timer off > while processing. The problem with this approach is that it frequently > hangs, and since it is written in FoxPro it has to run in the foreground. > That is why we are in the process of re-writing it as a .Net service. > >
Nick, Why would you not turn off the timer while running the processing? If your need is such, then perhaps a true multi-threaded model would be better than VFP. (I'm guessing your .Net service is going to be multi-threaded capable?) -- Michael J. Babcock, MCP MB Software Solutions, LLC http://mbsoftwaresolutions.com http://fabmate.com "Work smarter, not harder, with MBSS custom software solutions!" _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech ** 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.
