Computers keep getting faster, and databases keep getting larger. So as a "refinement" you could say, display something if a second or more has passed, and don't display anything if it hasn't.
We used to use MOD 100, which was fine 20 years ago. Now it spins by so fast you cant read it. -----Original Message----- From: dennis bartlett <[email protected]> To: U2 Users List <[email protected]> Sent: Tue, May 1, 2012 3:16 pm Subject: Re: [U2] READU vs READ I think you complicating things ... Troy has it right: Sure files could be resized, and code re-engineered, and all these good hing do help, but I reduced a process scanning 20 million records from 12 ays to 2 days just taking out the CRT to screen informing the user of rogress (or lack of progress.) on such a large number I'd set the interval to around 20000, so that the ode as below sits at n,count += 1 f rem(count,20000) then CRT n.count:' / ' : tot.count nd On 1 May 2012 11:03, Buss, Troy (Contractor, Logitek Systems) < [email protected]> wrote: > Good point... For progress indications, I tend to do the following on the mass updates: N.COUNT += 1 IF REM(COUNT, 1000) ELSE CRT "+": ______________________________________________ 2-Users mailing list [email protected] ttp://listserver.u2ug.org/mailman/listinfo/u2-users _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users
