Hi Bill, Not sure about the BindEvents() solution, but I implemented a timer-based one as you noted. It was designed to meet 200 requests in a day (nothing by anyone's standards). It polled the folder every minute when the timer triggered. I tested the solution I created with several hundred files and within a minute (with lots of time to spare) the process munched the data and pumped it into some FPD tables for the end users. So I was scalable to more than 1440 times the requirements. I developed this back in 2000 and just learned it was turned off. No changes required.
Our tester at the time liked to make developers cry. So he decided to dump 3,000 files into the folder thinking it would choke on it, then dumped another 5,000 once my process kicked off. My app turned off the timer munched the 3,000 in no time, turned the timer back on and munched the next 5K. I think it was the only time I was able to make him cry. <g> If he had only known I was using ADIR() all he had to do is drop 14K files into the mix and I would have been dead <g>. Anyway, I don't see any reason to get all fancy with BindEvents() when a timer works just fine. The only advantage to BindEvents() is to get instant processing instead of waiting until the next timer event. Rick White Light Computing, Inc. www.whitelightcomputing.com www.rickschummer.com _______________________________________________ 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.
