>>Wouldn't it brake an alignment with proportional fonts?
>>
>>>Change the report field expression to be character and delete the format expression. Instead, set the field expression to something like this:
>>>
>>>TRANSFORM(YourNumber, ICASE(FirstCondition=.t., '999.999', SecondCondition=.t., '9999.99', ThirdCondition=.t., '99999.9', '999999'))
>
>Yes .. If you're looking to align the decimal points, this would totally screw it up!

Actually, if properly padded, it shouldn't - at least IIRC the width of a space is supposed to be same as width of a digit. But then there may be fonts out there whose authors didn't feel like abiding to that rule - OK, just tried
_screen.FontName= "Sylfaen"
?"0123456 123"
?"01234560123"
and a few other fonts, and it doesn't align. Too bad - there was no good reason to remove this feature. Even the Arial, in which we are forced to compose messages here (l'II keep complaining about that one :) doesn't show the 123 in the example lines aligned.