Runtime vs. Development Foxpro Versions

[Gravey]

I've included the Foxpro About window in an application to display the Foxpro Version and System Information (_mst_about). However, I am concerned about the Foxpro version that this is displaying.

In the Development Environment and while running the application within development, the About Window displays "Microsoft Visual Foxpro 6.0 SP5" and the full version # as "06.00.8961.00" (the value returned by 'VERSION(4)'.

When the application is built and run in the Runtime Environment, the About Window displays "Microsoft Visual Foxpro 6.0" (no SP5) and the full version # is different "06.00.8167.00".

Should I be concerned about this difference? Why is there this difference? Does anyone know what support library this may come from? I can't seem to link it to any of the following: FOXUSER, VFP6R.DLL, & VFP6ENU.DLL.

Thanks for your assistance.
Sincerely,
Mike Graves

 

[rgbean]

The runtime version IS coming from VFP6R.DLL & VFP6ENU.DLL, and it should also be "06.00.8961.00". Check the path settings, and if these files are "registered", you'll need to check the user's system registry to find out where it might be getting the old version. The problem running the old version, is that 1) it won't have any of the fixes, 2) if you are using any new feature or variant, it may cause the program to not work correctly or even fail.

Rick

 

[Gravey]

Thanks for the insight Rich. It looks like VFP6ENU may be the culprit, I've found 2 different versions of that on my machine. One dated 5/7/99 and the other 8/18/00. The one in my windows\system directory was the older one. I replaced it with the newer one, but I'm still not seeing a difference when I do a Runtime on my machine, it still shows the older VFP version #. Development on my machine shows the newer VFP version #. If this information is being pulled from the registry, why are they different? -My computer only has one registry. How do I make sure this newer dll is "registered"? Thanks again for your assistance.

Mike

 

[rgbean]

Mike,
First, it's important to know that the version information doesn't come from the registry, it's in the file (Right Click, choose Propeties, click on the Version tab). What's in the registry may be a "path" setting to somewhere else where there exists a copy of the (wrong) file to use.

If you've used REGEDIT (and feel comfortable with being in it - you can do damage if you don't know what you're doing), just do a find on the files. There may be more than one entry - just check to see where they "point".

Rick

 

[Gravey]

Thanks Rick, I think we're getting somewhere - but I'm still more confused than ever. I check my registry and the path for these VFP6 DLLs is C:\Windows\System. I checked the properties of these DLLs and found the following results: the VFP6R.DLL is version 6.0.8167 (old); the VFP6RENU.DLL is also version 6.0.8167 (old); the VFP6ENU.DLL is version 6.0.8961 (new). I also checked the properties of these same files in my VFP98 folder and got the same results. Therefore, if I assume that development pulls the version number from the ENU dll and runtime pulls from the RENU dll then I guess the difference I am seeing in the About Windows makes sense. My question is now, how do I get updated VFP6R.DLL and VFP6RENU.DLL? Would reinstalling Service Pack 5 solve this problem? Is there some other VFP upgrade I need? Is there somewhere I can download these DLLs and just copy them in (or would that be a bad idea)? Thanks again Rick.

Mike

 

[Gravey]

Nevermind Rick. I reinstalled the SP5 and that worked. All my DLLs are the same version again! Thanks for you help.

Mike