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: paul@tpcqpc.com

-----Original Message-----

From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of

mbsoftwaresolutions@mbsoftwaresolutions.com

Sent: Monday, November 20, 2017 11:20 AM

To: profoxtech@leafe.com

Subject: Installing in your OWN folder instead of under Program Files (was

Re: AW: VFP9 latest service pack (9.0.0.7423))

On 2017-11-20 12:17, Koen Piller wrote:

> 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: ProFox@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.