>I am in a situation where I'm supporting a 3rd party product that has been modified by our company using strictly procedural code. Originally written in VFP6.0, we are attempting to port to VFP9.0 (but that's another story).
>I have to convince the IT director/coder and the CFO why it's better to use SQL-Select than the procedural code and why it's a bad thing to have over 2 million records in a file. The Select statement takes a much longer time to run than Seek ... Do While.. How can I present this to non-technical people?


Nancy, neither solution is "always better".

There actually are times when procedural Xbase code will be a better solution than SQL. But it may introduce hundreds of lines of code, each one potentially containing a bug, where a SQL command is one line of code to debug and maintain.

It's a constant balancing act.

Performance is a nut you can crack. The nut you cannot crack is inflexible management. ;-)