Actually, if you're using QM, Steve, you DO have another option. Their code
'writes' the FRX as a DBF, and you can search through the code to find the font they establish. I can't remember exactly how, but I did it for a client about 2 years ago.

Sorry about the Clipper app - I seem to be the harbinger of bad news when answering your messages, telling you what you CAN'T do instead of what you CAN.

Barbara

>Thanks, Barbara,
>
>I was afraid that was the answer. I'm using Query Maker, and it would makes sense for that kind of option to already be there if it were available. It also doesn't make sense that VFP doesn't have such a a setting on the Options dialog. It makes setting up self sizing reports on the fly more difficult when a lot of fields are needed.
>
>BTW, you answered my last inquiry here about Clipper tables, and it was much appreciated, even though I didn't get back to say thank you. As it turns out the Clipper tables are all Fox 2.x compatible, but are all built with non-structural CDXs. In addition, without adding a surogate key field there is no way to devise a PK on any of the tables as there is not any combination of fields which are reliably unique, and of course they are not even close to being normalized. Running the legacy app and a VFP app on the same data is probably not possible, and certainly not practical.