none
cannot locate the microsoft visual foxpro support library

    Question

  • Sorry; hope someone know to help me pls; 

    My error is "cannot locate the microsoft visual foxpro support library"

    and I downloaded VFP 9; and I Install successfull;

    but I dont know how to solve my error

    please help me

    thank alot

    Wednesday, February 08, 2012 3:01 PM

Answers

  • First Create An .EXE File Of Your Software.

    Than Copy The Following 3 Files Into Your Software Folder Where Your .EXE File Exists.

    File Names Are :

    1.    msvcr71.dll

    2.    vfp9r.dll

    3.    VFP9RENU.DLL

    These 3 Files Are Visual Foxpro 9.00's Library Supporting Files And You Will Find These Files Inside The VFP9 Folder.

    I Am Sure That This Will Definetely Solve Your Problem.

    Deepak Kharpate

    • Proposed as answer by Breeze10 Wednesday, February 18, 2015 11:55 AM
    • Marked as answer by Tom BorgmannEditor Monday, May 11, 2015 9:29 AM
    Saturday, February 11, 2012 5:34 PM
  • Hi,

    could you be a bit more specific on when this error occurs?

    Usually this only happens, when a compiled app is installed without corresponding runtimes.

    It might also be helpful to know, which windows version you are using and where exactly you installed VFP.


    Gruss / Best regards -Tom 010101100100011001010000011110000101001001101111011000110110101101110011

    Wednesday, February 08, 2012 3:09 PM
    Answerer

All replies

  • Hi,

    could you be a bit more specific on when this error occurs?

    Usually this only happens, when a compiled app is installed without corresponding runtimes.

    It might also be helpful to know, which windows version you are using and where exactly you installed VFP.


    Gruss / Best regards -Tom 010101100100011001010000011110000101001001101111011000110110101101110011

    Wednesday, February 08, 2012 3:09 PM
    Answerer
  • My error is "cannot locate the microsoft visual foxpro support library"

    This error appears when you are executing VFP application compiled into EXE. It should not appear on computer where VFP IDE is installed. Are you sure your EXE was created in VFP 9?

    You may also install VFP run-time from here: http://archive.msdn.microsoft.com/FoxPro/Release/ProjectReleases.aspx?ReleaseId=125


    Necessary run-time files are listed here: http://fox.wikis.com/wc.dll?Wiki~VFP9RuntimeFiles
    Wednesday, February 08, 2012 6:08 PM
    Moderator
  • Also, is it possible you have other versions of the VFP applications installed? If you had different version of VFP libraries installed, you may get conflicts, although the error will be different.

    For every expert, there is an equal and opposite expert. - Becker's Law


    My blog

    Wednesday, February 08, 2012 6:22 PM
    Moderator
  • First Create An .EXE File Of Your Software.

    Than Copy The Following 3 Files Into Your Software Folder Where Your .EXE File Exists.

    File Names Are :

    1.    msvcr71.dll

    2.    vfp9r.dll

    3.    VFP9RENU.DLL

    These 3 Files Are Visual Foxpro 9.00's Library Supporting Files And You Will Find These Files Inside The VFP9 Folder.

    I Am Sure That This Will Definetely Solve Your Problem.

    Deepak Kharpate

    • Proposed as answer by Breeze10 Wednesday, February 18, 2015 11:55 AM
    • Marked as answer by Tom BorgmannEditor Monday, May 11, 2015 9:29 AM
    Saturday, February 11, 2012 5:34 PM
  • Yes, my problem is solved after placing these files. Thanks!
    Saturday, May 24, 2014 1:10 PM
  • Pls how can i make the .EXE file 
    Wednesday, February 18, 2015 11:55 AM
  • Great solution! 

    Fast, simple and... that works!!! 

    Thank You,

    very, very much :-)

    Wednesday, February 25, 2015 10:54 PM
  • thanks sir but i did this with different way  copy these 3 files in c:\windows\system32 and its work  
    • Edited by HECTAR Monday, May 11, 2015 7:29 AM
    Monday, May 11, 2015 7:26 AM
  • ...which will only work on 32bit systems.

    The best place for DLLs is at the application folder, the rule to put runtimes into a system folder for all apps to use is outdated and not practical with many versions and putting them side by side into your app is a recommendation against DLL hell.

    http://en.wikipedia.org/wiki/DLL_Hell

    Quote: "If software developers need to customize a library, and if the main library release is unlikely to incorporate the changes that they need, they can ship the customized DLL for the program's private use (commonly by placing it in the program's private directory) or statically link the program against the customized library."

    It's not important whether it's libraries you design or runtime libraries, the different versions and their influence on other applications is, what matters. That's especially true for C++ runtime DLLs (there's more than msvcr71.dll) simply placing your version there does not only influence VFP apps. And also if other VFP Applications need other SP versions of the VFP DLLs, you don't do yourself a favor by putting runtimes into the system folder. So please, even if you are so sure this is better in your case, don't suggest doing it.

    What's true is, that VFP searches for runtimes in the EXE folder, the system folder (system32 or syswow64) and then the registry, whether the VFP runtimes are registered, which tells their location, too. The system folder is the system folder, it's for the system. The Program Files folder offers your application its own folder, make use of that.

    Bye, Olaf.


    Olaf Doschke - TMN Systemberatung GmbH

    http://www.tmn-systemberatung.de

    Monday, May 11, 2015 7:44 AM
  • Olaf is absolutely correct about this. You solutions is a NO GO as it only works on your system and may be obsolete within days or weeks (see Olafs post!)

    Gruss / Best regards
    -Tom
    Debugging is twice as hard as writing the code in the first place.
    Therefore, if you write the code as cleverly as possible,
    you are, by definition, not smart enough to debug it. 010101100100011001010000011110000101001001101111011000110110101101110011

    Monday, May 11, 2015 9:31 AM
    Answerer