Re: Eureka! I have found it!
Hi Graham,
> It's Rohans API Monitor
>
> http://www.rohitab.com/apimonitor
>
> been using it for years now, really useful (if confusing).
> It's a bit like ProcMon etc etc - the trick is getting the filters
> correct so you're not swampped with info.
>
> Although for something 'simple' like this turning everything on is a
> good place to start.
Thank you, and Rohan, so much! I will immediately add it to my arsenal!
Best regards,
--
Arnor Baldvinsson
Icetips Alta LLC
Re: Eureka! I have found it!
Arnor,
>
> Thank you, and Rohan, so much! I will immediately add it to my arsenal!
>
I am using it for years. One of my top favorites and even works on Windows
10.
Friedrich
Re: Eureka! I have found it!
Hi Graham,
> So I guess that's the change between earlier versions of Clarion and the
> later ones.
> The later ones detect the 740 error and try to overcome it by running
> ShellExecuteW
Yes, in C6.3 RUN() would just fail, don't think it even returned an
error, if you tried to run elevated process from a non-elevated one.
Best regards,
--
Arnor Baldvinsson
Icetips Alta LLC
Re: Eureka! I have found it!
Hi Graham,
> So I guess that's the change between earlier versions of Clarion and the
> later ones.
> The later ones detect the 740 error and try to overcome it by running
> ShellExecuteW
IIRC, there were numerous modifications to RUN() in C7 and later Clarion
versions. In C10, RUN() seems to call ShellExecute only if CreateProcess
failed (with Error 740).
CreateProcess can't determine whether an application needs to be elevated
via UAC, so SV added some fallback code here (maximum backward compatibility
to older Clarion versions?). The recommended solution would be the switch
to ShellExecute(Ex) only.
Friedrich