VFP9 latest service pack (9.0.0.7423)

[m***@mbsoftwaresolutions.com]

Installed VFP9 today on the corporate gig laptop. Trying to find the
runtimes to get me to 9.0.0.7423 (the last/latest/greatest). Followed
the links on
https://www.berezniker.com/content/pages/visual-foxpro/vfp-90-versions.

I'm at the 9.00.0000.5815 runtime but want the 7423 to be current.
(Yes, you can stop laughing now since "current" and "Visual FoxPro"
haven't been in the same church in over 13 years!) lol

wOOdy's old site no longer is operational. (That's where I got them in
the past.) I was on fox.wikis.com earlier which led me to the above
sites.

Suggestions?

tia,
--Mike

_______________________________________________
Post Messages to: ***@leafe.com
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/***@mbsoftwaresolutions.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.

[Koen Piller]

Google for VFPSp2 hotfix 3
Koen

Op vr 17 nov. 2017 om 23:39 schreef <

Post by m***@mbsoftwaresolutions.com
Installed VFP9 today on the corporate gig laptop. Trying to find the
runtimes to get me to 9.0.0.7423 (the last/latest/greatest). Followed
the links on
https://www.berezniker.com/content/pages/visual-foxpro/vfp-90-versions.
I'm at the 9.00.0000.5815 runtime but want the 7423 to be current.
(Yes, you can stop laughing now since "current" and "Visual FoxPro"
haven't been in the same church in over 13 years!) lol
wOOdy's old site no longer is operational. (That's where I got them in
the past.) I was on fox.wikis.com earlier which led me to the above
sites.
Suggestions?
tia,
--Mike

[excessive quoting removed by server]

_______________________________________________
Post Messages to: ***@leafe.com
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/CACUu1Su_M=HWOOwececJx1b9U8v_ZEYQgwV8SUOJqX7pe+***@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.

[Ted Roche]

http://www.foxpert.com/download/runtime.html

On Fri, Nov 17, 2017 at 5:40 PM,

Post by m***@mbsoftwaresolutions.com
Installed VFP9 today on the corporate gig laptop. Trying to find the
runtimes to get me to 9.0.0.7423 (the last/latest/greatest). Followed the
links on
https://www.berezniker.com/content/pages/visual-foxpro/vfp-90-versions.
I'm at the 9.00.0000.5815 runtime but want the 7423 to be current. (Yes,
you can stop laughing now since "current" and "Visual FoxPro" haven't been
in the same church in over 13 years!) lol
wOOdy's old site no longer is operational. (That's where I got them in the
past.) I was on fox.wikis.com earlier which led me to the above sites.
Suggestions?
tia,
--Mike

[excessive quoting removed by server]

_______________________________________________
Post Messages to: ***@leafe.com
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/CACW6n4tSDANJUP4E2+Nt=***@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.

[Jürgen Wondzinski]

the official landing page for my runtime installers is now
www.VFPX.org
This is the follow-up for the soon defunct Codeplex site.

wOOdy

-------- Ursprüngliche Nachricht --------
Von: Ted Roche <***@gmail.com>
Gesendet: Saturday, November 18, 2017 12:25 AM
An: ***@leafe.com
Betreff: Re: VFP9 latest service pack (9.0.0.7423)

Post by Ted Roche
http://www.foxpert.com/download/runtime.html
On Fri, Nov 17, 2017 at 5:40 PM,

Post by m***@mbsoftwaresolutions.com
Installed VFP9 today on the corporate gig laptop. Trying to find the
runtimes to get me to 9.0.0.7423 (the last/latest/greatest). Followed the
links on
https://www.berezniker.com/content/pages/visual-foxpro/vfp-90-versions.
I'm at the 9.00.0000.5815 runtime but want the 7423 to be current. (Yes,
you can stop laughing now since "current" and "Visual FoxPro" haven't been
in the same church in over 13 years!) lol
wOOdy's old site no longer is operational. (That's where I got them in the
past.) I was on fox.wikis.com earlier which led me to the above sites.
Suggestions?
tia,
--Mike

[excessive quoting removed by server]
_______________________________________________
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
** 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.

_______________________________________________
Post Messages to: ***@leafe.com
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/***@com.syntomo.email
** 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 th

[m***@mbsoftwaresolutions.com]

Post by Ted Roche
http://www.foxpert.com/download/runtime.html

Thought I had posted that link too, Ted. Yeah, I had gone there too but
it didn't give me the 7423 release. Thanks, though.

_______________________________________________
Post Messages to: ***@leafe.com
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/***@mbsoftwaresolutions.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.

[Richard Kaye]

I'm pretty sure you can get these via VFPx on Github.

--

rk

-----Original Message-----
From: ProfoxTech [mailto:profoxtech-***@leafe.com] On Behalf Of ***@mbsoftwaresolutions.com
Sent: Friday, November 17, 2017 5:40 PM
To: ***@leafe.com
Subject: VFP9 latest service pack (9.0.0.7423)

Installed VFP9 today on the corporate gig laptop. Trying to find the
runtimes to get me to 9.0.0.7423 (the last/latest/greatest). Followed
the links on
https://www.berezniker.com/content/pages/visual-foxpro/vfp-90-versions.

I'm at the 9.00.0000.5815 runtime but want the 7423 to be current.
(Yes, you can stop laughing now since "current" and "Visual FoxPro"
haven't been in the same church in over 13 years!) lol

wOOdy's old site no longer is operational. (That's where I got them in
the past.) I was on fox.wikis.com earlier which led me to the above
sites.

Suggestions?

tia,
--Mike

[excessive quoting removed by server]

_______________________________________________
Post Messages to: ***@leafe.com
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/***@MWHPR10MB1774.namprd10.prod.outlook.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.

[Jürgen Wondzinski]

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



-----Ursprüngliche Nachricht-----
Von: ProFox [mailto:profox-***@leafe.com] Im Auftrag von
***@mbsoftwaresolutions.com
Gesendet: Freitag, 17. November 2017 23:40
An: ProFox <***@leafe.com>
Betreff: VFP9 latest service pack (9.0.0.7423)

Installed VFP9 today on the corporate gig laptop. Trying to find the
runtimes to get me to 9.0.0.7423 (the last/latest/greatest). Followed
the links on
https://www.berezniker.com/content/pages/visual-foxpro/vfp-90-versions.

I'm at the 9.00.0000.5815 runtime but want the 7423 to be current.
(Yes, you can stop laughing now since "current" and "Visual FoxPro"
haven't been in the same church in over 13 years!) lol

wOOdy's old site no longer is operational. (That's where I got them in
the past.) I was on fox.wikis.com earlier which led me to the above
sites.

Suggestions?

tia,
--Mike

[excessive quoting removed by server]

_______________________________________________
Post Messages to: ***@leafe.com
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/017201d36218$abea42f0$03bec8d0$@wondzinski.de
** 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.

[m***@mbsoftwaresolutions.com]

Post by Jürgen Wondzinski
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.

_______________________________________________
Post Messages to: ***@leafe.com
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/***@mbsoftwaresolutions.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 obviou

[Jürgen Wondzinski]

Scan the disk for any VFP9*.dll and also the version of the MSVC*.DLLs.

-----Ursprüngliche Nachricht-----
Von: ProFox [mailto:profox-***@leafe.com] Im Auftrag von ***@mbsoftwaresolutions.com
Gesendet: Montag, 20. November 2017 17:15
An: ProFox Email List <***@leafe.com>
Betreff: Re: AW: VFP9 latest service pack (9.0.0.7423)


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: ***@leafe.com
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/01a801d3621a$f4b1a170$de14e450$@wondzinski.de
** 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 law

[Tracy Pearson]

Have a look at this message:
https://leafe.com/archives/msg/492151


Tracy


-----Original Message-----
From: ProfoxTech [mailto:profoxtech-***@leafe.com] On Behalf Of Jürgen Wondzinski
Sent: Monday, November 20, 2017 11:17 AM
To: ***@leafe.com
Subject: AW: AW: VFP9 latest service pack (9.0.0.7423)

Scan the disk for any VFP9*.dll and also the version of the MSVC*.DLLs.

-----Ursprüngliche Nachricht-----
Von: ProFox [mailto:profox-***@leafe.com] Im Auftrag von ***@mbsoftwaresolutions.com
Gesendet: Montag, 20. November 2017 17:15
An: ProFox Email List <***@leafe.com>
Betreff: Re: AW: VFP9 latest service pack (9.0.0.7423)


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.



_______________________________________________
Post Messages to: ***@leafe.com
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/000f01d3621d$4cc3a460$e64aed20$@powerchurch.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 wh

[m***@mbsoftwaresolutions.com]

Post by Jürgen Wondzinski
Scan the disk for any VFP9*.dll and also the version of the MSVC*.DLLs.

I'll check it out tonight. I thought if I dropped the vfp9r.dll and
vfp9t.dll in the App's folder directly, it would override whatever else
was on the machine. Apparently not!

_______________________________________________
Post Messages to: ***@leafe.com
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/***@mbsoftwaresolutions.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 s

[Richard Kaye]

Per wOOdy, check the Common Files location of Program Files for the runtime DLLs.
--
rk

-----Original Message-----
From: ProfoxTech [mailto:profoxtech-***@leafe.com] On Behalf Of ***@mbsoftwaresolutions.com
Sent: Monday, November 20, 2017 11:15 AM
To: ***@leafe.com
Subject: Re: AW: VFP9 latest service pack (9.0.0.7423)

Post by Jürgen Wondzinski
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.

_______________________________________________
Post Messages to: ***@leafe.com
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/***@MWHPR10MB1774.namprd10.prod.outlook.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 obv

[m***@mbsoftwaresolutions.com]

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.

Post by Richard Kaye
Per wOOdy, check the Common Files location of Program Files for the runtime DLLs.
--
rk
-----Original Message-----
Sent: Monday, November 20, 2017 11:15 AM
Subject: Re: AW: VFP9 latest service pack (9.0.0.7423)

Post by Jürgen Wondzinski
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: ***@leafe.com
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/***@mbsoftwaresolutions.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 tho

[Koen Piller]

What is the directory of app not C:/Program Files (86) I hope
Rgds
Koen


Op ma 20 nov. 2017 om 18:02 schreef <

Post by m***@mbsoftwaresolutions.com
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.

Post by Richard Kaye
Per wOOdy, check the Common Files location of Program Files for the runtime DLLs.
--
rk
-----Original Message-----
Sent: Monday, November 20, 2017 11:15 AM
Subject: Re: AW: VFP9 latest service pack (9.0.0.7423)

Post by Jürgen Wondzinski
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: ***@leafe.com
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/CACUu1Styh5pdicc93+TKr2YsYbAD+***@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

[m***@mbsoftwaresolutions.com]

Post by Koen Piller
What is the directory of app not C:/Program Files (86) I hope
Rgds
Koen

Oh hell no....I haven't deployed to Program Files for YEARS. Many here
will tell you that you avoided so many M$ problems by installing in your
own app folder off the root (C:\MBSS) instead of following M$'s advice.
Chime in all, if you want to give an "amen" for that.

_______________________________________________
Post Messages to: ***@leafe.com
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/***@mbsoftwaresolutions.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.

[Paul H. Tarver]

I agree with you, I do not install anything in Program Files or other
Microsoft suggested locations. In fact, I've been building old school style
for a while now. Where possible, I am installing all files in my own folders
including avoiding installing anything in the Registry. You all will
probably laugh at this strategy, but hear me out.

Yes, there is a Santa Clause and yes, I still store settings in .INI files.
Here's why: I write software utilities that often have to be moved by
clients either between computers or from local drives to network shares. All
my data is stored in a sub-folder below the program installation folder as
are all supporting files. Main program files and settings files are stored
in the program installation folder, including MSVCR71.DLL and MSVCP71.DLL to
support vfpcompression.fll and other elements like the VFP runtimes also
stored in my main program folder. The only files I install outside of this
main folder or subfolders are MSCOMCT2.OCX and MSCOMCT2.SRG which provide
the Calendar popup I use (and one day when I have nothing else to do, I'll
find a replacement I like and get rid of that too, but in the meantime I
include an installer just for that if the user happens to move our program
and need the OCX installed.)

The IT admins that I work with have told me explicitly that they love the
flexibility our method of programming gives them particularly in a corporate
environment where change is a given. They can move our programs by copying a
single folder and updating a shortcut. They can add a new user by creating a
shortcut and they can change a server or workstation out without breaking
our program. AND, they can back up one folder and if there is a crash, copy
that folder to a new hard drive and start running the application
immediately.

I've never bought in to the whole idea of storing my stuff in someone else's
environment. Laugh if you like, but it works for me and it works for my
clients. Obviously, building a true Client-Server system requires different
mindset since you'll need a database server, but for what I make the most
money on today, my strategy works for me.

Paul H. Tarver
Email: ***@tpcqpc.com


-----Original Message-----
From: ProfoxTech [mailto:profoxtech-***@leafe.com] On Behalf Of
***@mbsoftwaresolutions.com
Sent: Monday, November 20, 2017 11:20 AM
To: ***@leafe.com
Subject: Installing in your OWN folder instead of under Program Files (was
Re: AW: VFP9 latest service pack (9.0.0.7423))

What is the directory of app not C:/Program Files (86) I hope Rgds
Koen

Oh hell no....I haven't deployed to Program Files for YEARS. Many here
will tell you that you avoided so many M$ problems by installing in your
own app folder off the root (C:\MBSS) instead of following M$'s advice.
Chime in all, if you want to give an "amen" for that.

[excessive quoting removed by server]

_______________________________________________
Post Messages to: ***@leafe.com
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/038201d36229$a6ed0a10$f4c71e30$@tpcqpc.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.

[m***@mbsoftwaresolutions.com]

Post by Paul H. Tarver
I agree with you, I do not install anything in Program Files or other
Microsoft suggested locations. In fact, I've been building old school style
for a while now. Where possible, I am installing all files in my own folders
including avoiding installing anything in the Registry. You all will
probably laugh at this strategy, but hear me out.
Yes, there is a Santa Clause and yes, I still store settings in .INI files.
Here's why: I write software utilities that often have to be moved by
clients either between computers or from local drives to network shares. All
my data is stored in a sub-folder below the program installation folder as
are all supporting files. Main program files and settings files are stored
in the program installation folder, including MSVCR71.DLL and
MSVCP71.DLL to
support vfpcompression.fll and other elements like the VFP runtimes also
stored in my main program folder. The only files I install outside of this
main folder or subfolders are MSCOMCT2.OCX and MSCOMCT2.SRG which provide
the Calendar popup I use (and one day when I have nothing else to do, I'll
find a replacement I like and get rid of that too, but in the meantime I
include an installer just for that if the user happens to move our program
and need the OCX installed.)
The IT admins that I work with have told me explicitly that they love the
flexibility our method of programming gives them particularly in a corporate
environment where change is a given. They can move our programs by copying a
single folder and updating a shortcut. They can add a new user by creating a
shortcut and they can change a server or workstation out without breaking
our program. AND, they can back up one folder and if there is a crash, copy
that folder to a new hard drive and start running the application
immediately.
I've never bought in to the whole idea of storing my stuff in someone else's
environment. Laugh if you like, but it works for me and it works for my
clients. Obviously, building a true Client-Server system requires different
mindset since you'll need a database server, but for what I make the most
money on today, my strategy works for me.

Hi Paul,

My strategy is very similar to yours. I still use INI files and they
work great for the reasons you stated!

--Mike

_______________________________________________
Post Messages to: ***@leafe.com
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/***@mbsoftwaresolutions.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.

[Paul H. Tarver]

Glad to know I'm not in the wilderness on that point! :)

Paul H. Tarver
Email: ***@tpcqpc.com



-----Original Message-----
From: ProfoxTech [mailto:profoxtech-***@leafe.com] On Behalf Of
***@mbsoftwaresolutions.com
Sent: Monday, November 20, 2017 12:12 PM
To: ***@leafe.com
Subject: Re: Installing in your OWN folder instead of under Program Files
(was Re: AW: VFP9 latest service pack (9.0.0.7423))

Post by Paul H. Tarver
I agree with you, I do not install anything in Program Files or other
Microsoft suggested locations. In fact, I've been building old school
style for a while now. Where possible, I am installing all files in my
own folders including avoiding installing anything in the Registry.
You all will probably laugh at this strategy, but hear me out.
Yes, there is a Santa Clause and yes, I still store settings in .INI files.
Here's why: I write software utilities that often have to be moved by
clients either between computers or from local drives to network
shares. All my data is stored in a sub-folder below the program
installation folder as are all supporting files. Main program files
and settings files are stored in the program installation folder,
including MSVCR71.DLL and MSVCP71.DLL to support vfpcompression.fll
and other elements like the VFP runtimes also stored in my main
program folder. The only files I install outside of this main folder
or subfolders are MSCOMCT2.OCX and MSCOMCT2.SRG which provide the
Calendar popup I use (and one day when I have nothing else to do, I'll
find a replacement I like and get rid of that too, but in the meantime
I include an installer just for that if the user happens to move our
program and need the OCX installed.)
The IT admins that I work with have told me explicitly that they love
the flexibility our method of programming gives them particularly in a
corporate environment where change is a given. They can move our
programs by copying a single folder and updating a shortcut. They can
add a new user by creating a shortcut and they can change a server or
workstation out without breaking our program. AND, they can back up
one folder and if there is a crash, copy that folder to a new hard
drive and start running the application immediately.
I've never bought in to the whole idea of storing my stuff in someone
else's environment. Laugh if you like, but it works for me and it
works for my clients. Obviously, building a true Client-Server system
requires different mindset since you'll need a database server, but
for what I make the most money on today, my strategy works for me.

Hi Paul,

My strategy is very similar to yours. I still use INI files and they work
great for the reasons you stated!

--Mike

[excessive quoting removed by server]

_______________________________________________
Post Messages to: ***@leafe.com
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/03f301d3622f$9e292d40$da7b87c0$@tpcqpc.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.

[Charlie-gm]

Oh hell no....I haven't deployed to Program Files for YEARS.  Many
here will tell you that you avoided so many M$ problems by installing
in your own app folder off the root (C:\MBSS) instead of following
M$'s advice.  Chime in all, if you want to give an "amen" for that.

Amen.

The best "architectural" decisions I've made on the Windows platform
have been those that have directly contradicted Microsoft "best
practice" statements.

Of course, when I mean best decision, I'm evaluating based on ease of
deployment, maintenance, upgrade, and error-tracing. Many of my
applications have run since Windows 98. Apart from coding to take
advantage of newer VFP features, I pretty much never had to spend time
fixing the design because of something MS did (although around the time
of Vista there was MessageBox() weirdness and "ghost" files...). I
compare that to what I've seen in massive rewrites of COM+,
Net<something... right after COM+?>, IE (browser-based) code (but
browsers were supposed to save us from that???!!! - ROFLMAO) - all
because of Windows version changes (or even just IE changes).

But, in agreement with Ted, if I was solely out to just keep a job due
to MS-created breakage, my decisions were probably not the best.
Hmmm.... I wonder if MS labeled those things as "best practices" because
they were best for MS: as in the best way to lock-in development staff
on Windows (play on laziness and lack of computer science knowledge),
and therefore lock-in the user base. Maybe MS wasn't as stupid as they
appeared to be.... Nah.

-Charlie


_______________________________________________
Post Messages to: ***@leafe.com
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/a47479f1-89d4-9ea3-3ca2-***@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

[AndyHC]

Hasn't anyone worked out a way to slipstream the sp's onto VFP9?

_______________________________________________
Post Messages to: ***@leafe.com
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/f62735fc-6224-45e1-8c1d-***@hawthorncottage.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.

[Richard Kaye]

If for some reason the runtimes got installed in the Common Files location, you will need to update or delete them. For example, if you have used the VFP dev installer it will put the runtimes there. And they will take precedence over the runtimes in the folder with your EXE.

--

rk

-----Original Message-----
From: ProfoxTech [mailto:profoxtech-***@leafe.com] On Behalf Of AndyHC
Sent: Monday, November 20, 2017 12:22 PM
To: ***@leafe.com
Subject: Re: AW: VFP9 latest service pack (9.0.0.7423)

Hasn't anyone worked out a way to slipstream the sp's onto VFP9?

[excessive quoting removed by server]

_______________________________________________
Post Messages to: ***@leafe.com
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/***@MWHPR10MB1774.namprd10.prod.outlook.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.