>If you come up with two or more approaches on how to solve a particular >problem and you are not sure which would be faster, then you can easily >construct a speedtest to see which is best.
I agree with Irv, with some additional comments. Sometimes it's worth it to squeeze that extra little performance out of a routine. A lot of times it isn't, though. Generally, when a program is running, 90% of the processor time will be spent in 10% of your code. That's the part you want to optimize. When I want to get a really accurate reading on performance tests, I try to eliminate all variables. I do the following: - Test from a projector, not the authoring environment. - Quit all other programs - Log off and disconnect from the network physically. Pull the plug on your modem. - On Windows, use ctrl-alt-del to kill *all* processes except systray and explorer Cordially, Kerry Thompson [To remove yourself from this list, or to change to digest mode, go to http://www.penworks.com/LUJ/lingo-l.cgi To post messages to the list, email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED]) Lingo-L is for learning and helping with programming Lingo. Thanks!]
