>>>>>> [...]
>>>>>>albert
>>>>>>
>>>>>>>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.
>>>
>>>
>>>I think so as well
>>>
>>>There are a few solutions - read the pdf on this page http://www.atoutfox.com/articles.asp?ACTION=FCONSULTER&ID=0000000845
>>>It's in French
>>>
>>
>>Thanks, Gregory.
>>
>>In our case, running as an administrator is enough and all the wiser. Anyway, we only need to elevate when working with our COM server projects, not with our regular application projects, so it's not really a nuisance. But if it were a reasonable and applicable alternative...
>
>Possibly an additional VFP link that starts a special fpw - prg combination with the only goal to compile the pjx and quit? So the admin thing is only for the moment of compiling....

That's an interesting idea, to have an external builder explicitly requiring elevation that is ran instead of the normal builder. I believe this can be hooked to the project itself, so it can be set on a project-by-project basis and launched normally in an IDE session.

Thanks, Lutz, this seems good food for thought!