John,
FoxReg fixed the problem. Thanks a bunch for the tip!
>Jim,
>
>I don't think REGSVR32 will help with this problem (though you might as well try it). I think your problem is that some registry information was overwritten and you no longer have the right entries for a design-time license for the control. REGSVR32 will only take care of run-time licensing. That means if you had an application that used the control it would work, but you can't create an application that uses the control.
>
>Go to the files section here and find FoxReg.exe. Download and run it. It will fix your registry entries.
>
>>>>I read this post the other day:
>>>>
>>>>"The MAPI Session and Message controls that come with VFP work pretty well. They have a decent help file. The only limitation is that they work only with MAPI compliant mail systems".
>>>>
>>>>Here's my problem:
>>>>I wanted to play with these and saw that the mapi controls were not available to me. I went into Tools/Options/Controls and added the mapi OCX's which were in my WINNT directory. I assumed these are the ones that VFP installed. They now show up on my ActiveX toolbar but when I try to drop them on a form I get ole "error code, appropriate license for this class not found." What's my next step?
>>>
>>>Jim,
>>>
>>>Go tothe commadn window in NT and switch to your NT directory. Then type REGSVR32
and press enter. You should get a message syaing the server has been registered. Then you should be able to use those controls.
>>
>>Jim,
>>Thanks, that works registering an OCX. How would I identify which ActiveX control goes with which OCX. I can't do a REGSVR32 *.ocx, so I have to do them one at a time. Until I get the time to do this, how would I figure out which ocx's are for MS mapi session control, MS mapi message control (or any other specific control) in VFP. The TOOLS/OPTIONS/CONTROLS view only lists the ActiveX name, not the ocx file. I registerd msmapi32.ocx succesfully, but I still can't use either of the two Mapi controls (I restarted VFP). I assume that they must be using other ocx files.
