I love hearing how other people do their work, it makes me think about new ways and reminds me that my ways are not the only ways!
I have several .prg files that I automatically attach to projects as not included files that do things like generate my table re-index/re-build procedures, a modified gendbc to generate code to re-create tables, and even a script I use a lot to create Field Lists and Create Cursor scripts. Adding an Init.prg file would be an easy way to handle the settings like you describe. I think investigating the project hook to auto-run the prg would be worth the time though!
Paul H. Tarver Tarver Program Consultants, Inc.
-----Original Message----- From: Dave Crozier [mailto:DaveC@Flexipol.co.uk] Sent: Wednesday, May 17, 2017 2:41 AM To: profoxtech@leafe.com Subject: RE: Running Multiple Instances of VFP 9
Paul, I have a standard of adding an "init.prg" to every project which sets the default folder to that current project home folder and then also sets up any settings required such as exact, date, ansii etc.
It soon becomes second nature to run the init program when a project is open or when some of the settings have been hosed in development mode when programs have crashed. I was going to generate a project hook to auto run it on open but have never bothered.
Dave
-----Original Message----- From: ProFox [mailto:profox-bounces@leafe.com] On Behalf Of Paul H. Tarver Sent: 16 May 2017 18:00 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]