On 10/09/2017 08:03, Leslie wrote:
> "John Wright" <john@jfwright.co.uk> wrote in message
> news:5d7b66b7-3b26-ea1e-3c9b-182525581b19@jfwright.co.uk...
> 
>> Paradox for some reason installed
>> as elevated. But I have overcome this by using the hack in the registry.
> 
> Which sort of brings us full circle.
> 
> My point being that as an IT person surely you are curious as to why the
> situation has arisen in the first place. The Registry hack may not continue
> to work in the future which makes you vulnerable. We have a precedent:  the
> opportunistic locking registry hack no longer works.
> 
> So, within this thread you now have enough information to try and figure out
> why Paradox is running elevated and therefore take true corrective action to
> prevent it running elevated instead of relying on a registry hack.
> 
> I also wonder what would happen if another BDE application runs on the
> machine at the same time but cannot run elevated. I have previously seen a
> similar conflict where Paradox was running in compatibility mode which
> forced the BDE into compatibility mode as well. Then when another BDE
> application ran, it failed because it did not like compatibility mode.
> Crystal Reports struggled with the compatibility mode with the BDE for
> example.
> 
> So, IMO you really need to understand what has occurred rather than relying
> upon magic to keep things going for you.
> Take control !!
> 
> 
> 
> 
Thanks for this followup Leslie. Good point you raise, I will get into 
this when I have more time.

John Wright