> That kind of optimization sounds encouraging. You were a good friend to go > through that much code! > > I appreciate your offer. Do you remember what type of problems you found > in your friend's code ? We've gone through this code pretty thoroughly - > there's some good programming experience behind it. I think that it was mainly loop optimizations, with very little in the way of calculation optimizations. The data was indexed differently, the SEEK() function was repeatedly used (to replace 6 or more lines of code). That type of thing. No real rocket science, but worth a look from someone who wasn't too closely involved. > Our code is a few thousand lines. A large part of the code does a complex > simulation of a user-defined manufacturing process and walks through the > process (sometimes 500 steps) taking branches and iterative loops, > determining labor needs, equipment usage, number/cost of units produced, > etc. My head swims at getting anyone up to speed on the whole thing. The > rest of the code is more straight forward, relating tables and making > calculations. That section would be more realistic to take a look at. > Perhaps I could get a code sample to you and see if anything jumps out at > you. Sure. prussell@fox.nstn.ca