VFP9 SP1 runtime files

[teresas]

I have several in-house apps running on a Novell network. The application .exe files are on a network drive, and the VFP 9 runtime files have been installed to the user workstations using Inno Setup. During the transition from VFP 7 to VFP 9, having both sets of runtime files installed was not a problem, since the dll files have different names. However, what will happen with SP1 for VFP 9, where the dll files have not been renamed? Should the runtime files be updated on all workstations before I do any new builds with VFP 9 SP1? Or can I have a mix of updated workstations and updated applications until everything is at SP1?

I ran a quick test with unexpected results. I thought I’d get the error about “library files not found” when I started up an application built with VF9 SP1 on a workstation without the SP1 runtime files, but I didn’t. So, are there any issues to be concerned about if the transition to SP1 is a little bumpy (other than whether I was expecting a specifc bug to be fixed)?

Teresa

 

[JimWWinter]

Teresa,

Per Ken Levy, in a message on the UT, "If the Service Pack 1 runtime allows an older compiled EXE/APP to run without a binary mismatch error, the results are unpredictable and this is not recommended. There is no way to know for sure. We did not change the language and did not add any new commands/functions, so it may or may not work OK. But this is not supported (do this at your own risk)."

Good luck,
Jim

 

[teresas]

Okay, thanks for your reply, Jim!

Teresa

 

[teresas]

Here's a follow-up question:

As an interim solution, what if I copied the new runtime files into the same directories as the exe files that have been built using SP1? Wouldn’t VFP ignore the older versions on the workstations (but they would still be available for exe files that haven’t yet been updated)? And then once all of my apps have been converted to SP1, install the runtime files onto the workstations as usual?

Teresa

 

[dbMark]

Remember that when you make the transition from VFP 9 to the free sp1 recently released, remember to update those runtimes you distributed with your applications (app, exe or dll) to ensure safest operation.

REQUIRED DLLs and dates with VFP 9 sp1:

vfp9r.dll 11/04/2005 6:13 PM
vfp9t.dll 11/04/2005 6:13 PM
vfp9renu.dll 11/04/2005 5:44 PM
msvcr71.dll (should be 02/21/2003 or newer *)
gdiplus.dll (must be 08/04/2004 or newer *)

* Note that I found many copies of these last two files all over my C: drive (of different sizes and dates) but it is best to use the latest recent version. Be aware that some companies change the date stamp in their application folders and files, so don't let dates be the sole factor you consider when locating the most recent version. One way to see the version number is (in XP) to view the files in Windows Explorer and hover the mouse over the file and a tool-tip will appear listing the file version.

See also faq184-4421 How do I distribute a VFP application?

What I do is place my DLLs in the same folder as the EXE. It may not be elegant but it is simple and seems to work well.

dbMark

 

[JimWWinter]

You can also get service pack run time installers at ftp://ftp.prolib.de/public/.

Regards,
Jim

 

[teresas]

One way to see the version number is (in XP) to view the files in Windows Explorer and hover the mouse over the file and a tool-tip will appear listing the file version.

And in Windows 2000, you can right-click, select Properties, and go to the Version tab. For msvcr71.dll, all copies on my PC are version 7.10.3052.4. I copy msvcr71.dll (and only this runtime file) in the same folder as the exe, since that was the instructions I found in Rick Borup's "Deploying VFP Apps with Inno Setup" whitepaper. The other runtime files get installed on the workstation in the applicable system directories. (But I think I will be changing this procedure temporarily until all of my apps are built with VFP9 SP1.)

As for gdiplus.dll, the filestamp on the various copies on my PC are earlier than what dbMark recommended. The version is 5.1.3102.1360. However, I'm wondering if that doesn't really matter in a Windows 2000 environment, since Microsoft's Application Distribution Process says this:

Gdiplus.dll is only installed on platforms prior to Windows 2000 (for example, Windows 98).

You can also get service pack run time installers at ftp://ftp.prolib.de/public/

I just might try these out. I'm curious if the "silent mode" switch works, since my LAN manager couldn't get InnoSetup to run silently from the log in script.

Teresa

 

[Dan Freeman]

The reason for the date requirement on gdiplus.dll is that's when they released a hot-fix for a security flaw.