>Hilmar,
>
>Surely, in the day of the 2+ghz system costing $499. or less, this consideration arises far less frequently than it did in the past, wouldn't you think?
>
>Today I think that speed is relative to I/O more than anything else by far and designs that minimize actual I/O and optimize whatever I/O is necessary are the key when performance is a critical issue.
>
>cheers
Yes, I am sure it is not relevant in most cases. And yet, there are cases where you need peak performance, even with faster machines... fortunately, I haven't seen the need (for myself, as a programmer) to make this necessary. Also, the fact that a single VFP command can internally do quite a lot (for instance, SELECT - SQL would presummably translate into several complicated, nested loops) not only lets me program with few commands, it also turns out to be faster than anything which I would likely program.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
