Good Morning,
Have several legacy VFP6 applications my users run. A mixed bag of VFP6 and VFP9 generated executables.
The main application everyone can run, have another executable in a folder under the main application, most people can run. Now have a new person who cannot run the one in the sub folder, he can run the main!
Checked the folder where the other application runs and have located vfp6 and vfp7 dll's, including the respective versions of the "renu" dll's in the same folder. The shortcut starts the correct exe and starts where the dll's are located? It "should" run.
Does anyone see anything blatantly wrong?
Regards, Desmond
--- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html ---
Do you have an installer to do all the copying/registering etc? I think you have to have some files installed on the machine even to use the runtime.
What error (if any) do you get?
Peter Cushing IT Department WHISPERING SMITH
On 02/06/2016 14:35, Desmond Lloyd wrote:
Good Morning,
Have several legacy VFP6 applications my users run. A mixed bag of VFP6 and VFP9 generated executables.
The main application everyone can run, have another executable in a folder under the main application, most people can run. Now have a new person who cannot run the one in the sub folder, he can run the main!
Checked the folder where the other application runs and have located vfp6 and vfp7 dll's, including the respective versions of the "renu" dll's in the same folder. The shortcut starts the correct exe and starts where the dll's are located? It "should" run.
Does anyone see anything blatantly wrong?
Regards, Desmond
--- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html
[excessive quoting removed by server]
Do you have an installer to do all the copying/registering etc? I think you have to have some files installed on the machine even to use the runtime.
There's a C++ dll that is required in addition to the runtime, and I think one other file, at a minimum. If all of the required files are located in the same folder as the .exe you want to run, it will run, no "installation" or registration necessary.
It's possible that the other machines have a PATH environmental variable set that the problem machine doesn't.
Ken Dibble www.stic-cil.org
Thank you for the quick response... Yes I have installers for both VFP6 and VFP9 (thank you Woodie) Turns out I needed to install the VFP9 runtimes, right as rain! As an aside, I have yet another "report shell" application that was running just fine prior to installing the runtimes. Go figure...
Thanks again, Desmond
On 2 June 2016 at 08:51, Ken Dibble krdibble@stny.rr.com wrote:
Do you have an installer to do all the copying/registering etc?
I think you have to have some files installed on the machine even to use the runtime.
There's a C++ dll that is required in addition to the runtime, and I think one other file, at a minimum. If all of the required files are located in the same folder as the .exe you want to run, it will run, no "installation" or registration necessary.
It's possible that the other machines have a PATH environmental variable set that the problem machine doesn't.
Ken Dibble www.stic-cil.org
[excessive quoting removed by server]
Desmond Lloyd wrote on 2016-06-02:
Thank you for the quick response... Yes I have installers for both VFP6 and VFP9 (thank you Woodie) Turns out I needed to install the VFP9 runtimes, right as rain! As an aside, I have yet another "report
shell"
application that was running just fine prior to installing the runtimes. Go figure...
Thanks again, Desmond
Desmond,
I wrote a CMD file to search and display the versions of all the VFP9 runtime DLLS. We used to use it frequently with customers. Here is a link to the file, it doesn't paste well due to line wrapping.
http://powerchurchsoftware.com/support/versions.cmd
On the fifth line, you can adjust the vfp9*.dll to just vfp*.dll to get all runtimes.
A quick explanation of the inner workings is: It creates a VBS file, then the FOR loop searches the drive and runs the VBS file for each file matching found. The VBS file echoes the filename, location, and version to the command window Then the VBS file is removed. Then the window pauses, allowing one to just dbl-click the CMD file.
Tracy Pearson PowerChurch Software
-
Desmond Lloyd -
Ken Dibble -
Peter Cushing -
Tracy Pearson