Thank you, George(including the directions-- I need to get my boss to cough up the $$$ for membership :->). I do believe this will work, but I can't test it right now, as the development schedule is packed-- we sell turnkey systems, so we can manually go into 'C:\Windows\Fonts\' on all our systems if we need to. Thanks again!

>>Excuse my ignorance, but could you spell out what I need to send to SendMessage to inform them? The documentation in MSDN is quite verbose. :-> Thanks.
>
>I understand completely. However, rather than repeating it here, I'd suggest you look at Ed Rauh's FAQ #7812. To find it, click the Knowledge Base icon (purple book), select "Frequently Asked Questions", then Win32 and Other APIs. Ed's article is entitled "How do I add fonts to Windows programmatically?" It includes what you need to do with the SendMessage function.
>
>>> A third possibility does come to mind. I've only utilized this with the FoxPro >report designer. So what is going on with VFP interally with
>>> @...SAY is unknown to me.
>>
>>Possible, I guess. If I could simply open up 'C:\WINDOWS\FONTS\' in a window and then close it without the installer seeing, that would work great. I'd think there'd be a function that could be called to do whatever doing that does(probably updating the registry, I'd guess). Thank you for your help.
>
>Personally, I wish we could do this kind of stuff from VFP (permanent install, that is). But since we can't, this is the next best thing.