>>>>>
>>>>>>Run VFP9 as Administrator (you can set it permanently on the shortcut under the Right-click properties, and Compatibility tab, and "Run this program as an administrator."
>>>>
>>>>Run VFP9 as Administrator is a bad idea. You should rather solve the issue then circumvent it. Any programm that needs to run as admin is to be moved to the NULL device. We do not live in the 80's any more.
>>>>
>>>
>>>Lutz,
>>>
>>>I believe there must be an OLEPUBLIC class somewhere on Albert's project. When the project is built, the class is (re-)registered in the system. As far as I know, in W10 you must have special privileges to do that, but if you know of some other way to build an OLEPUBLIC class without running the IDE as administrator, I too would gladly use that.
>>
>>Not much OLEPUBLIC with me.
>>Make the OLESERVER load an other app. So the server is just an wrapper. (no idea if a VFP server can SET CLASSLIB an external app)
>>Run VFP dev in a Virtual Machine running an appropriate OS.
>>
>>Start fund-raising to ask Chen to remove the auto register bug / feature.
>>
>>HTH :)
>>
>>Lutz
>
>I think it's a feature that matches the overall spirit of VFP. You build something, then you can use it right away from the command line... I wouldn't ask Chen to use his precious time on this :-)

The idea is a switch - autoregister off for those who prefer to work as non elevated user. Those who like the risk should use on?