https://www.screencast.com/t/ZWpHnejMqdZ3
What the heck? Auto-upgrade code that had been working is suddenly not, but what's more bizarre is the system telling me there's a log file when the screenshot clearly shot's there NOT any such file.
Am I going crazy?
Mike,
Since your VFP app runs in the context of a regular user, it is not allowed to WRITE into the ProgramFiles tree. That's a standard Windows Security feature since Vista. For older software, which does not adhere to those security guidelines, those write attempts are rerouted to the "VirtualStore", so that the old software does not generate an error. The regular user/application does not see any difference, since the "VirtualStore" is an overlay to the real filesystem. Only if you look with activated Admin-Mode, then you see a difference.
Each user has it's own VirtualStore area, you find it at %Appdata%\Local\VirtualStore\
(You know that you can use Environment variables like %temp% or %Windir% directly at the Explorers path textbox?)
wOOdy
-----Ursprüngliche Nachricht----- Von: ProFox [mailto:profox-bounces@leafe.com] Im Auftrag von mbsoftwaresolutions@mbsoftwaresolutions.com Gesendet: Samstag, 9. Dezember 2017 00:47 An: ProFox profox@leafe.com Betreff: VFP9rerr.log file supposedly created...but not there
Additionally: Why are you using an outdated VFP9 runtime? The latest and greatest runtime is version 7423 from 3.April 2009 Are you keen to explicitely experience even more than your own software errors? Or what else reasons hinder you to just run that damn VFP9SP2RT.exe runtime installer and be more errorfree?
Get your copy from www.vfpx.org
wOOdy
On 2017-12-09 04:10, Jürgen Wondzinski wrote:
Additionally: Why are you using an outdated VFP9 runtime? The latest and greatest runtime is version 7423 from 3.April 2009 Are you keen to explicitely experience even more than your own software errors? Or what else reasons hinder you to just run that damn VFP9SP2RT.exe runtime installer and be more errorfree?
Get your copy from www.vfpx.org
wOOdy
This is from an installation where their app (supplied by their Corporate...which happened to be the last app I delivered when I was still at Sylvan back in 2009) used VFP9SP1. I can't recall why it wasn't upgraded to SP2 (7423) back then? I explored the idea of updating those runtimes awhile back but those efforts failed in C00000005 errors (or some other C0000? code) so I reverted to their previous DLL files. The lead developer over me insisted on Installshield (although I would have used Inno).
On 2017-12-09 04:10, Jürgen Wondzinski wrote:
Additionally: Why are you using an outdated VFP9 runtime? The latest and greatest runtime is version 7423 from 3.April 2009 Are you keen to explicitely experience even more than your own software errors? Or what else reasons hinder you to just run that damn VFP9SP2RT.exe runtime installer and be more errorfree?
Get your copy from www.vfpx.org
wOOdy
This is from an installation where their app (supplied by their Corporate...which happened to be the last app I delivered when I was still at Sylvan back in 2009) used VFP9SP1. I can't recall why it wasn't upgraded to SP2 (7423) back then? I explored the idea of updating those runtimes awhile back but those efforts failed in C00000005 errors (or some other C0000? code) so I reverted to their previous DLL files. The lead developer over me insisted on Installshield (although I would have used Inno) and he used the M$ suggested best practice locations instead of putting the runtimes right into the app's folder.
Security as a guess. I don't think you can write to that folder anymore.
On Fri, Dec 8, 2017 at 5:46 PM, <mbsoftwaresolutions@mbsoftwaresolutions.com
wrote:
https://www.screencast.com/t/ZWpHnejMqdZ3
What the heck? Auto-upgrade code that had been working is suddenly not, but what's more bizarre is the system telling me there's a log file when the screenshot clearly shot's there NOT any such file.
Am I going crazy?
[excessive quoting removed by server]
-
Jürgen Wondzinski -
mbsoftwaresolutions＠mbsoftwaresolutions.com -
Stephen Russell