Yupp, Exe good, Dll bad was and is my take on 32/64 bit issues. Made me wonder as well,
https://github.com/git-for-windows/git/wiki/32-bit-issues
was only thing that registered as possible problem on quickgoogling.

regards
thomas

>What problem are you trying to solve here?
>
>Anything that uses the CreateProcess API under the covers should be able to run 32 or 64 bit applications no problem. These are external processes so there should be no issue launching either. This is handled by Windows and it knows what to do based on the PE header of the EXE it's launching.
>
>ShellExecute(), raw CreateProcess() API, cmd, pwsh, and even the Fox Run command all should work to launch either 32 or 64 bit code.
>
>The only time 32/64 bit is an issue if you load something in-process: DLLs and COM Objects mainly.
>
>+++ Rick ---
>
>>Hi.
>>
>>Any idea how to tell VFP to run a 64bit program?
>>
>>I use API_AppRun to run a git with several parameters - this is for Bin2Text on VFPX
>>
>>The problem is git (if somebody like to test)
>>It could be installed as 64bit or 32bit
>>
>>So if it is a 32bit installation, I can run, for example git log -1>temp.txt via APPRun.
>>This fails if installed as 64bit. I can call cmd calling git, like cmd /c git log -1>temp.txt but that's so awkward.
>>
>>So what do I need to do that VFP can call the 64bit program?
>>
>>Lutz