>Like some of the followup messsages have said, this a bug in VFP.
> Over the last 4 days I have gone through hell trying to figure this
>one out, and even re-loaded my note book 3 times from scratch (FDISK
>AND EVERYTHING).
>
>The bottom line for me is that with a virgin install of NT 4.0 (no
>service packs or anything) and a virgin install of VFP 5.0 (minus the
>paradox drivers of course) I could not use the mapi ole control.
> (The easiest way to find out if it works it to try to MODI FORM the
>sendmail form in the .\vfp\samples\solution\ole directory. If you can
>see a send mail button on the form you don't have a problem, but I
>will bet everyone does.). My anecdotal experience is that VFP 5.0
>(at least under NT 4.0) can NOT USE MICROSOFT ACTIVEX CONTROLS!
>
>The Microsoft tech I just got off the phone gave me the necessary
>registry key to make it work. However, since it IS a license issue he
>told me that I am not allowed to tell you what the key and value is.
> You will have to call Microsoft and get it from them.
>
>The Microsoft guy did not debit my developer-network support calls
>over the issue, so don't let them charge you for showing you how to
>make the software you already paid for work!!
>
>[SMTP:foxpro@transformation.com]
>
>
>When I attempt to use some of my ActiveX controls, I get the following
>error: "OLE error code 0x80040112: Appropriate License for this class
>not
>found." What does this mean? Are there additional things to pay for
>when
>using these controls, or have I misplaced some files? If so, what
>files?
>Thanks for any help.

I just spent the better part of my afternoon with Microsoft working on this, and after speaking to a couple of different people, this is the problem: the OFFICE 97 install removes the licenses for these controls. Reinstalling VFP and/or Re-registering your ocx's does nothing to remedy the problem. You have to manually re-enter the licenses in the registry. Works like a charm first time through. If you have this problem, call them and tell them that this is what you need to do... don't let 'em give you the run around, and don't let them decrement your support calls or charge you. This is their problem, not ours to pay for.