Ok, well at least that makes some sense. It was built into a startup module that would have been used for everyone - I guess they figured why not register it.

>As I understand it, that key is required to be able to use the OCX successfully at design time e.g. drop it on a form - if not present, those design operations fail. I'm not sure if the key needs to be present on user machines for runtime use.
>
>>Hi Al,
>>
>>Thanks. I did not get that match on a google search. So I just went ahead and inserted the registry entry anyhow - even though have no idea what it means. I just need it in there so that this 3rd party app (old version of Foxfire) will start up without a problem. My guess is that it is obsolete code that has been never stripped out of their startup program.
>>
>>Albert
>>
>>>Searching Google on the license key/GUID led me to this: https://www.tek-tips.com/viewthread.cfm?qid=394236
>>>
>>>>Am having to rewrite a small stub of a very old VFP program that installs a couple of .ocx files (rewriting because it assumed the \system32 folder when it should now be \syswow64). It has some code to make sure a license key is inserted into the registry for "Fox Reg". It does not actually try to install an .ocx for said "Fox Reg" but it wants this key to be available. I searched various spots and could not find a component named Fox Reg.
>>>>
>>>>Ring a bell with anyone? What product is it referring to? I looked in the VFP installation folder as well in this product's folder but could not find an .ocx or .dll of that name. I am just curious - I can modify the code to continue to check for that key but kinda like to know what it is doing while I am at it.
>>>>
>>>>Here is the license key and value if that makes any difference:
>>>>
>>>>DB4C0D00-400B-101B-A3C9-08002B2F49FB
>>>>value: mgkgtgnnmnmninigthkgogggvmkhinjggnvm
>>>>
>>>>Albert