>Yuk! That doesn't sound too appealing to me either. I have this method implemented in a VFP 3.0b app that has been in production for about 2 years. There is no noticeable performance hit. And, assuming that you didn't (gasp!) use VFP base classes, you need only add some variation of this code to the Init method of your base form class. The only problem that I found was that olebound controls did not seem to like the SetAll.Fontsize business.

Okay, thanks...sounds like it's worth a try (yes, we do still have some base forms...oh well :) but I can likely make common method to run from my top-level application object, anyway...