I've been reading through previous postings about the need to distribute and Register VFP Runtime DLL's with the VFP EXE file.
First some background, The MS Visual Studio installed is Visual Studio Professional which included VFP6
I have compiled my VFP6 EXE file as a:
* Win32 Executable/Com Server (EXE)
and when executed, the Build runs fine.
I can even export the EXE file into another non-VFP development Test directory on my own PC where it runs as expected and well.
My question is -- Do I really need to include these files with my distributed EXE file when I send it to a customer?
I have searched my entire system to find these DLL files and they are not installed on my PC anywhere.
So, where do these DLL's come from?
vfp6renu.dll
vfp6r.dll
And lastly -- are there other issues (OS considerations, other file inclusions, etc.) that need to be considered/included when distributing a VFP EXE file onto another PC which has never seen VFP?
Thanks,
I_Forgot
First some background, The MS Visual Studio installed is Visual Studio Professional which included VFP6
I have compiled my VFP6 EXE file as a:
* Win32 Executable/Com Server (EXE)
and when executed, the Build runs fine.
I can even export the EXE file into another non-VFP development Test directory on my own PC where it runs as expected and well.
My question is -- Do I really need to include these files with my distributed EXE file when I send it to a customer?
I have searched my entire system to find these DLL files and they are not installed on my PC anywhere.
So, where do these DLL's come from?
vfp6renu.dll
vfp6r.dll
And lastly -- are there other issues (OS considerations, other file inclusions, etc.) that need to be considered/included when distributing a VFP EXE file onto another PC which has never seen VFP?
Thanks,
I_Forgot