>>Ummm... I wasn't too clear in the first reply. I don't mind using the number of characters instead of pixel width - chopping it into lines with MLine() has the advantage of respecting the embedded CRs in the message string - and I chop it first, and then measure the lengths in pixels. It also doesn't matter if one line is longer than another - it's not a right justified text, it's just a replacement for a message box. I've just had this problem that I used a read only editbox to display the message, and it's size was pretty (ugly?) unpredictable.
>>
>>BTW, I've made it in the meantime, using an array of labels, and it works (and looks) much nicer - margins are easier to calculate, works fine with any font name/size combination I tried it with. I'll post it here in Files as soon as I translate comments into English and supply some demonstration prg. And... as soon as I learn how's the new way of uploading actually working.
>
>Sounds like a workable solution. I'll be looking for it in Files...

It's in the Files since Thursday/Friday (depending on timezone) or so, I think it's in Classes/VCX, look for alert.zip. Requires FoxTools.

BTW, the "New policy ... effective 1st of October" was misleading somewhat - I've sent it to file@levelextreme.com, and when apparently nothing happened, tried through the Web interface, and it kept me waiting with no prepared mail form. The thing actually goes the other way 'round: click first, fill up the data, and then send it to file@UT.