I use INNO to package the VFP & C++ runtimes as well as some third party 
libraries I use and put all that in the same folder as my EXE instead of common 
files.

I doubt MS gives it that much thought. 

--
rk


-----Original Message-----
From: profoxtech-boun...@leafe.com [mailto:profoxtech-boun...@leafe.com] On 
Behalf Of Allen
Sent: Tuesday, January 17, 2012 8:10 AM
To: profoxt...@leafe.com
Subject: Re: VFP9 SP2 problem

That is correct Richard. But I took the update from a web site as an install 
supposed to be the latest, but it seems it was not and did not update 2 out of 
3 files.
I also heard briefly from my client, who tried the same update on an XP 
machine, including all the 7423 files. He says its all 7423 but this time its 
reversed in that the app can not see files in a directory. I wonder if we need 
different runtimes for XP.

I have yet to talk to him as he is on travels. I wonder sometimes if Microsoft 
is trying to shoot VFP9 developers.
Al

-----Original Message-----
From: Richard Kaye
AFAIK, the last update to VFP SP2 (9.00.0000.7423) was back in 2006. It was a 
post-SP2 hot patch and basically required you to manually copy the new VFP9.exe 
to wherever you have VFP installed; update the common files location with the 
new DLLs; and finally update the MSM files if you are using that to package the 
runtimes for distribution.


[excessive quoting removed by server]

_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: 
http://leafe.com/archives/byMID/profox/DF1EEF11E586A64FB54A97F22A8BD0441D4A5EE4E4@ACKBWDDQH1.artfact.local
** 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.

Reply via email to