>>>I'm only a sporadic UT visitor, so apologize for a question that I'm sure has been asked before:
>>>I have some legacy (2.x) reports that I would like to convert to current format and tweak, rather than
>>>rewriting the same reports from scratch. Can someone point me to a real good writeup of
>>>the issues involved in converting reports? Or should I just flat-out forget about doing that?
>>>
>>I believe your reports should work as is in the new environment.
>>Copy them all under new folder and just open them all and save. Make sure the Printer is not checked. Then try running them. Hopefully there would not be any surprises.
>
>Thank you for the reply, Naomi. In the old days, I would use something like CHR(160) for a
>non-blank, non-printing character, but I don't think I can use that trick anymore. What
>is the recommended way to achieve that now?

Chr(32) instead - there's no such thing in Windows; chr(160) may work the same, but you can't be sure, it can be translated by any piece of code - a .nls translator, VFP itself, it may run on a machine with a different codepage and that character may be a printable etc etc.

Depending on what were you achieving with that under DOS, you may or may not find a way to emulate that now - and maybe you won't need to. Most of the kludges we applied then became unnecessary in the world of proportional fonts.