Sorry, but you did not add a new argument. Still from my point of view (I know, that field name should not have spaces at the end) it is incorrect code implementation. If stored in the structure table, I would retrive field names with alltrim().

>>Jim,
>>
>>There are neither contrary opinion nor hesitation, criticism or personal affront in my first reply. Please read it carefully. I was curious and still do not see the reason why the code was written in such a way.
>>Anyway we are on the forum and I believe, we are free to express our opinions unless they harm anybody.
>
>
>He was reporting that code that worked in previous versions, didn't work in VFP 8. Whether it should have worked or should not have worked is actually not the issue here. But I can think of more than one reason you could have a problem here, as often code is run where a definition is stored in a table. If the name is part of the definition (almost certain to be the case) then any names smaller than the length of the field will be followed by spaces. If I used those field names to create and then execute a CREATE CURSOR command, it will still work as it will ignore the trailing spaces. If that type of behaviour were to be the norm, I would have quite a bit of additional coding to do for VFP 8 because if it no longer ignoring trailing spaces. I think the code shown, is just a way of showing the behaviour, which is likely caused by data definitions stored in tables.