I definitely can see where you would benefit from EM based on the way you work. I can also see where managing so many projects might seem messy, but one man's mess is another man's office, right?
My projects usually start with a short, steep development cycle then migrate to a long term support. My process is to create self-contained project folders for each project with the exception of links to a global .vcx file and some re-useable forms and graphics. Once a project is complete and the client is live, then the project folder is archived to a different storage area for ongoing support. Using the shortcuts and relative path references enable those settings to remain the same regardless of where the files are stored.
Somehow the process works for me and I suspect everyone on this list has their own "process" for using VFP. In my opinion that is one of the best recommendations for VFP: there are lots of ways to solve just about any problem.
Paul H. Tarver Tarver Program Consultants, Inc.
-----Original Message----- From: Richard Kaye [mailto:rkaye@invaluable.com] Sent: Tuesday, May 16, 2017 12:08 PM To: profoxtech@leafe.com Subject: RE: Running Multiple Instances of VFP 9
I missed in the thread where you mentioned the scope of your variations. EM might be a bit clunky under those conditions. :-) OTOH hundreds of shortcuts or navigating around also sounds a bit messy. IAC config.fpw and startup PRGs will also do the trick.
My own personal dev setup involves the ability to run with a specific customers set of business rules. So I use EM for the overall environment (i.e. SET commands, etc.) and a PRG that lets me select the path of the environment I want to test in via a plain old DBF. Besides the pathing it also swaps out a customer specific class library as needed.
--
rk
-----Original Message----- From: Paul H. Tarver [mailto:paul@tpcqpc.com] Sent: Tuesday, May 16, 2017 1:00 PM To: Richard Kaye rkaye@invaluable.com; profoxtech@leafe.com Subject: RE: Running Multiple Instances of VFP 9
Admittedly, I don't know a lot about the Environment Manager, but what I've seen of it so far, it would be lots more work to configure than my solution for the way I work.
The Environment Manager looks like a good idea if you have smaller number of large projects you need to work on a regularly. My situation is I have hundreds of individual projects sharing most of the same Option settings, but I need to control default search paths and relative paths independently. And those paths may change frequently as projects move through our development process. However, I can see where the Environment Manager could be very useful for the right person.
Thanks for the reminder.
Paul H. Tarver Tarver Program Consultants, Inc.
-----Original Message----- From: Richard Kaye [mailto:rkaye@invaluable.com] Sent: Monday, May 15, 2017 6:41 AM To: profoxtech@leafe.com Subject: RE: Running Multiple Instances of VFP 9
I know you've come up with a good solution that works for you but I thought I'd mention that the situation you're describing is exactly what the Environment Manager is for.
--
rk
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Paul H. Tarver Sent: Friday, May 12, 2017 6:22 PM To: profoxtech@leafe.com Subject: RE: Running Multiple Instances of VFP 9
I guess the deal is that if I open VFP by clicking on a .PJX file, it seems to always open in the same dev environment, but if I open VFP by clicking on the VFP icon, I can get a new development environment. The challenge is that because I work on so many different projects I use unique config.fpw files to set the paths and other custom settings for each project. That means if I start the project from the folder where the config.fpw is located, all the settings are controlled by the config.fpw stored in that folder. However, if I start the program from the icon, it loads the standard default settings which are not necessarily what I need for each specific project.
I think what I was really asking was whether there was a setting that would force VFP to open new projects in a new development environment. Kind of like right clicking on a link and choosing to open the page in a new tab or a new window.
Paul H. Tarver Tarver Program Consultants, Inc. Email: paul@tpcqpc.com
[excessive quoting removed by server]