>>>Interesting find - when I elevate VFP to use administrator, I no longer have access to my mapped drives from within foxpro. Must be because those are mapped using my "regular" credentials and since VFP is now running under a different account, Windows blocks access to those drives. That is, I could not do:
>>>
>>>

USE F:\Claims\Apps.dbf

>>>
>>>once VFP was elevated. If I went out to Win explorer, the table is there. But if I try to browse to it from within VFP, even issuing
>>>
>>>

USE ?

>>>
>>>the dialog would come up and for a second, you could see the mapped drive and then it disappeared.
>>>
>>>I will set the shortcut back to not use the administrator level and just live with the dialog regarding the registry - it would not be the first or only time I have had to click through a dialog box :-)
>>>
>>>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.

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