Thanks all for the quick responses. Did I mention this was an ancient client install?
It was looking for VFP6 runtimes. Apparently, the previous dev had upgraded all of the other apps and their runtimes but this little exe (it's around 10 lines of code) was ignored and kept running fine until they replaced the machine. This was an old box, sitting around in a corner, mostly just run once a month. A Dell Pentium III, running Windows 2000. Manufacturing date: 10/2000. They sure don't build 'em like they used to! The Process Explorer let me peek at the strings in the EXE (modi file would have, too, I suppose) and VFP6 was right there. Rebuilt the exe to VFP7 to match the rest of the installation. Tested and working fine. Thanks again. On Fri, Feb 3, 2017 at 11:19 AM, Peter Cushing <[email protected]> wrote: > Just checked one of my install scripts and it installs: > > msvcr70.dll in one script and msvcr71.dll in another. Not sure why at the > moment. > vfp7renu.dll > vfp7r.dll > plus some other rich text controls etc but think they are optional. > > HTH > > Peter Cushing > IT Department > WHISPERING SMITH > > > > On 03/02/2017 15:51, Richard Kaye wrote: >> >> I believe it's one or more of the VFP runtime dlls (vfp#.dll, vfp#enu.dll, >> assuming English resource). Are the DLLs in the folder with your EXE or >> otherwise in the path? >> >> -- >> >> rk >> -----Original Message----- >> From: ProfoxTech [mailto:[email protected]] On Behalf Of Ted >> Roche >> Sent: Friday, February 03, 2017 10:47 AM >> To: [email protected] >> Subject: "Cannot locate the Microsoft Visual FoxPro Support Library" >> >> Hey, kids: >> >> I know I've gotten this working before, but it's Friday, and my IQ >> decreases exponentially as the weekend approaches. >> >> Ancient client install that mostly runs VFP7 SP1. They have a little >> utility app they run monthly to archive data. It's been "moved" to a >> new machine by one of their IT techs. Both the main app, running in >> VFP7SP1, and vFoxRun run fine on this machine, but clicking on this >> .EXE throws the error in the subject line. >> >> If I run the .EXE from the vFoxRun command window, it also runs okay. >> Hunh, what? >> >> I tried running regsvr32 on all the files in the c:\Program >> FIles\Common Files\Microsoft\VFP folder. I downloaded the VFP7SP1 and >> VFP9SP2 runtime installers from CodePlex. All ran with no errors. >> >> I don't recall the pedigree of the file. Is there any way we can get >> it to tell us what it is looking for? >> >> Up-to-date Windows 7 SP1 32-bit Dell Optiplex 9020, 4 Gb of RAM, black. >> >> What am I missing, besides the weekend? >> > > > > This communication is intended for the person or organisation to whom it is > addressed. The contents are confidential and may be protected in law. > Unauthorised use, copying or disclosure of any of it may be unlawful. If you > have received this message in error, please notify us immediately by > telephone or email. > www.whisperingsmith.com > > Whispering Smith Ltd Head Office:61 Great Ducie Street, Manchester M3 1RR. > Tel:0161 831 3700 Fax:0161 831 3715 > London Office:17-19 Foley Street, London W1W 6DW Tel:0207 299 7960 > > > > [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/cacw6n4u_yv2jqghojo9zfazz4o2ruzteaiyets2md3cans7...@mail.gmail.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
