>>>Economical. Fix some other stuff in grids, combos, odd behavior of some controls when in grids etc - look at Fabio's list.
>>
>>Economical? It's my guess that repairing this bug will cost no more than half a day work (the morning from 9 till lunch), including extensive alpha and beta testing. It must be a piece of cake for Calvin and its mates. As soon as they look at the code they all yell "HERE, this loop needs a little repair, that's all!".
>
>Actually, I'd think it'd be a "HERE... before entering this loop"... but I agree with the rest.
>
>>The repair I have in mind will generate a _cliptext with the field names on line 1, even if there are no records. So, never an empty result. And that's the way I want it, because I need those field names for a report, even if there are no records.
>
>Here our habits diverge - I specifically DO NOT want these field names. I don't want my user to see any field names. I'll provide meaningful captions for the report. Actually, I'd rather see these field names vanish, but then it's just two lines to get rid of them, so I don't mind.
>
>And... the time we've (collectively) spent on this subject is already more than what it'd take Calvin's gang to fix this AND give us the option (like a fourth parameter in .datatoclip() which would be, bitwise, HeaderOn/Off).
>
>This begins to sound like a scholastic dispute, but I enjoyed it nevertheless.

Let's disagree to agree. :)