You cannot include the runtime file inside an exe (at least you can but it will have no effect). The runtime files are DLLs that need to but registered in Windows seperately. If you are using InstallShield to distribute your application, just select the runtime files at the "Obects/Merge modules" section of the preparation.
I do it the cheap/easy way. Most of our programs are written in VFP6, but a few have been done over in VFP7. Rather than making a whole new install program, I just copy the following files to the windows system folder (c:\windows\system or c:\winnt\system32). I haven't gotten one error from any of our VFP7 .exe files.
Ron,
You're either very lucky, or all the systems that run your applications are fairly new. On "older" systems, a number of system support files may need to be added and/or updated or the VFP runtimes will act "flaky" or simply fail. Also, by not registering these components, it'll make the system "work" harder to fire up your application, and potentially allow another application to register their versions of these files, so your application won't use your files at all!
Copying files is not a substitute for using a good installer for your Windows applications.
true, copying files is not the way either, but it was a quick way to get a couple of apps running on management's win2000 cpu's ("do it yesterday" type of thing).
For production, we will have a new "base install" program.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.