That's where I was at first. I replaced the PF(x86)\Common
Files\Microsoft Shared\VFP files. Then after that failed, I put them
directly in the App's folder (which I usually always do by default). No
luck...C-5 errors either way.
I'm betting the problem is with a MCVCR7*.dll file mismatch perhaps.
On 2017-11-20 11:22, Richard Kaye wrote:
Per wOOdy, check the Common Files location of Program Files for the
runtime DLLs.
--
rk
-----Original Message-----
From: ProfoxTech [mailto:[email protected]] On Behalf Of
[email protected]
Sent: Monday, November 20, 2017 11:15 AM
To: [email protected]
Subject: Re: AW: VFP9 latest service pack (9.0.0.7423)
On 2017-11-20 11:00, Jürgen Wondzinski wrote:
The VFP runtime installers have been on VFPX since 2014, and just have
transitioned to www.VFPX.org (which will always point to the actual
archives)
The current direct download link from there is
https://github.com/VFPX/VFPRuntimeInstallers/blob/master/VFP9SP2RT.exe
wOOdy
Thanks to you and everyone else who helped on this. I was able to
update my local dev machine to 9.0.0.7423. I wanted to update a
client's installation but when I tried replacing the vfp9t.dll and
vfp9r.dll, it made the installed app just throw C00000005 errors on
startup. Their app was installed with Installshield (barf) back in
2009. Was hoping to upgrade them via this kind of change as I don't
have access to the Installshield package.
[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/[email protected]
** 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.
