>>
>>>To the other comments, I want to add that VFP treats variables as an interpreter does, not as a compiler. This is not serious in practice, but it does have two drawbacks:
>>
>>That's because VFP is interpreted.
>
>Craig,
>
>Don't mean to be picky here, but, by definition, VFP most definitely is not an interpreted language. It produces tokenized threaded p-code. An interpreter is forced to re-evaluate the source code each time the program loaded. While this does happen with macro expanision, this is the only time such occurs. I know you know this, but I just wanted to clarify the subject for those who do not.

Worse than that, George, it will re-interpret each line in a loop, for example, for every iteration of that loop. That is what makes interpreters so sllooooowww. mmm... maybe that is what you said...?