I know you are probably tired of hearing from me on this stuff, but I'm still working out the issues with my ProjectSetup.exe tool that I described last week that creates a shortcut and a .FPW file for my projects so I can run multiple instances of VFP for multiple projects at the same time. I've reworked the .FPW file command order so it now looks like this:
**************************************************************************** *****
TMPFILES=c:\temp
EDITWORK=c:\temp
SORTWORK=c:\temp
PROGWORK=c:\temp
PATH = .\DATA; .\FORMS; .\GRAPHICS; .\LIBS; .\MENUS; .\PROGRAMS; .\REPORTS; T:\LIBRARY
DEFAULT = "T:\DATAWORKS\ACTIVE\TP\FORMAL"
RESOURCE = "T:\DATAWORKS\ACTIVE\TP \FORMAL\FOXUSER.DBF"
COMMAND = MODIFY PROJECT "T:\DATAWORKS\ACTIVE\TP \FORMAL\TRNSLATE.PJX" NOWAIT
**************************************************************************** *****
However, the NOWAIT option appears to have no effect because once VFP opens, the project manager shows my project it but there is also open a command window with nothing in it and I cannot type in the command window until I close it and re-open the command window. It's like once VFP starts with COMMAND = MODIFY PROJECT "T:\DATAWORKS\ACTIVE\TP \FORMAL\TRNSLATE.PJX" it stays focused on the project manager until I close the command window and restart it. Then it works normally. It's almost like there's a READ EVENTS statement that is active until I close the blank command window. FYI, I've also tried this by modifying the FPW file to read COMMAND = DO PROJSTART.PRG, , but it does exact the same thing even if I include the NOWAIT option on the Modify Project line.
It's not a big deal, I can close the command window and re-open it but it annoys me that the NOWAIT option is there and by the documentation, it should solve the problem I'm seeing.
Anyone have any ideas about what I'm doing wrong here?
Paul H. Tarver Tarver Program Consultants, Inc. Email: mailto:paul@tpcqpc.com paul@tpcqpc.com
--- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html ---
On Mon, Jun 19, 2017 at 7:28 PM, Paul H. Tarver paul@tpcqpc.com wrote:
COMMAND = MODIFY PROJECT "T:\DATAWORKS\ACTIVE\TP \FORMAL\TRNSLATE.PJX" NOWAIT
COMMAND is a key-value pair and the NOWAIT isn't parsed.
You should probably use
COMMAND = MyStartup.App
and write a little APP or PRG or EXE to do all the things you want, load menu options, set shortcut keys, (I've got an OKL, for example) and MODI PROJ Trnslate.PJX NOWAIT.
I tried the .prg route before, but I re-did it based on your recommendation just in case I did something wrong.
Here's what I have set up now:
start-vfp9x64.FPW file: ************************************************************* TMPFILES=c:\temp EDITWORK=c:\temp SORTWORK=c:\temp PROGWORK=c:\temp
PATH = .\DATA; .\FORMS; .\GRAPHICS; .\LIBS; .\MENUS; .\PROGRAMS; .\REPORTS; T:\LIBRARY
DEFAULT = "T:\ACTIVE\TPM " RESOURCE = "T:\ ACTIVE\TPM \FOXUSER.DBF" COMMAND = do "T:\ ACTIVE\TPM \start-vfp9x64.prg" *************************************************************
start-vfp9x64.prg ************************************************************* CLEAR MEMORY CLOSE DATA CLEAR ALL CLOSE ALL SET SYSMENU TO DEFAULT
CD " T:\ ACTIVE\TPM" MODIFY PROJECT trnslate.pjx NOWAIT ACTIVATE WINDOW COMMAND *************************************************************
When I start VFP from the shortcut, the .FPW is processed and the .PRG is run, the project manager opens with the correct project, a blank command window opens and I cannot type in the command window because every keystroke is passed directly to the project manager. Once I close the blank command window, I can open a new command window and everything works normally. Same results that I get if I issue the MODIFY PROJECT command directly from the .FPW.
Interestingly, if I open VFP in the folder and I type 'do start-vfp9x64.prg' in the command window, the project manager opens normally with the correct project info and goes immediately back to the regular command window ready for my next input. In other words, it looks like the problem may be in the .FPW file. So, I went back to the .FPW file and removed everything except the PATH and COMMAND lines. Same result. I also noticed that when I close the blank command window and file named _command.prg is created in the project folder.
This is getting personal now. Uggghhhh.
Paul H. Tarver Tarver Program Consultants, Inc. Email: paul@tpcqpc.com
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Ted Roche Sent: Monday, June 19, 2017 7:25 PM To: profoxtech@leafe.com Subject: Re: Modify Project from Config.FPW
On Mon, Jun 19, 2017 at 7:28 PM, Paul H. Tarver paul@tpcqpc.com wrote:
COMMAND = MODIFY PROJECT "T:\DATAWORKS\ACTIVE\TP \FORMAL\TRNSLATE.PJX" NOWAIT
COMMAND is a key-value pair and the NOWAIT isn't parsed.
You should probably use
COMMAND = MyStartup.App
and write a little APP or PRG or EXE to do all the things you want, load menu options, set shortcut keys, (I've got an OKL, for example) and MODI PROJ Trnslate.PJX NOWAIT.
-- Ted Roche Ted Roche & Associates, LLC http://www.tedroche.com
[excessive quoting removed by server]
Hi Paul,
the file _command.prg will contains the commands history and VFP places it in the same folder as foxuser.dbf / fpt.
Don't delete it and retry!
Gianni
On Tue, 20 Jun 2017 10:20:29 -0500, "Paul H. Tarver" paul@tpcqpc.com wrote:
I tried the .prg route before, but I re-did it based on your recommendation just in case I did something wrong.
Here's what I have set up now:
start-vfp9x64.FPW file: ************************************************************* TMPFILES=c:\temp EDITWORK=c:\temp SORTWORK=c:\temp PROGWORK=c:\temp
PATH = .\DATA; .\FORMS; .\GRAPHICS; .\LIBS; .\MENUS; .\PROGRAMS; .\REPORTS; T:\LIBRARY
DEFAULT = "T:\ACTIVE\TPM " RESOURCE = "T:\ ACTIVE\TPM \FOXUSER.DBF" COMMAND = do "T:\ ACTIVE\TPM \start-vfp9x64.prg" *************************************************************
start-vfp9x64.prg ************************************************************* CLEAR MEMORY CLOSE DATA CLEAR ALL CLOSE ALL SET SYSMENU TO DEFAULT
CD " T:\ ACTIVE\TPM" MODIFY PROJECT trnslate.pjx NOWAIT ACTIVATE WINDOW COMMAND *************************************************************
When I start VFP from the shortcut, the .FPW is processed and the .PRG is run, the project manager opens with the correct project, a blank command window opens and I cannot type in the command window because every keystroke is passed directly to the project manager. Once I close the blank command window, I can open a new command window and everything works normally. Same results that I get if I issue the MODIFY PROJECT command directly from the .FPW.
Interestingly, if I open VFP in the folder and I type 'do start-vfp9x64.prg' in the command window, the project manager opens normally with the correct project info and goes immediately back to the regular command window ready for my next input. In other words, it looks like the problem may be in the .FPW file. So, I went back to the .FPW file and removed everything except the PATH and COMMAND lines. Same result. I also noticed that when I close the blank command window and file named _command.prg is created in the project folder.
Gianni,
Yes, I've seen that file before, I just threw that tidbit in the mix in case it helped us figure this problem out.
Thanks!
Paul H. Tarver Tarver Program Consultants, Inc. Email: paul@tpcqpc.com
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Gianni Turri Sent: Tuesday, June 20, 2017 10:59 AM To: profoxtech@leafe.com Subject: Re: Modify Project from Config.FPW
Hi Paul,
the file _command.prg will contains the commands history and VFP places it in the same folder as foxuser.dbf / fpt.
Don't delete it and retry!
Gianni
On Tue, 20 Jun 2017 10:20:29 -0500, "Paul H. Tarver" paul@tpcqpc.com wrote:
I tried the .prg route before, but I re-did it based on your recommendation just in case I did something wrong.
Here's what I have set up now:
start-vfp9x64.FPW file: ************************************************************* TMPFILES=c:\temp EDITWORK=c:\temp SORTWORK=c:\temp PROGWORK=c:\temp
PATH = .\DATA; .\FORMS; .\GRAPHICS; .\LIBS; .\MENUS; .\PROGRAMS; .\REPORTS; T:\LIBRARY
DEFAULT = "T:\ACTIVE\TPM " RESOURCE = "T:\ ACTIVE\TPM \FOXUSER.DBF" COMMAND = do "T:\ ACTIVE\TPM \start-vfp9x64.prg" *************************************************************
start-vfp9x64.prg ************************************************************* CLEAR MEMORY CLOSE DATA CLEAR ALL CLOSE ALL SET SYSMENU TO DEFAULT
CD " T:\ ACTIVE\TPM" MODIFY PROJECT trnslate.pjx NOWAIT ACTIVATE WINDOW COMMAND *************************************************************
When I start VFP from the shortcut, the .FPW is processed and the .PRG is run, the project manager opens with the correct project, a blank command window opens and I cannot type in the command window because every keystroke is passed directly to the project manager. Once I close the blank command window, I can open a new command window and everything works normally. Same results that I get if I issue the MODIFY PROJECT command directly from the .FPW.
Interestingly, if I open VFP in the folder and I type 'do start-vfp9x64.prg' in the command window, the project manager opens normally with the correct project info and goes immediately back to the regular command window ready for my next input. In other words, it looks like the problem may be in the .FPW file. So, I went back to the .FPW file and removed everything except the PATH and COMMAND lines. Same result. I also noticed that when I close the blank command window and file named _command.prg is created in the project folder.
[excessive quoting removed by server]
Paul,
I use a PRG. I am not seeing the behavior you are talking about.
In my PRG, I do reset the location and widths of the windows I have open. Properties, Document View and DataSession are docked together. Then the Command Window is docked under them. These are all docked to the right side of the screen. I have this because I will occasionally remote in to my computer. The laptop resolution is smaller than the desktop.
Tracy Pearson PowerChurch Software
Paul H. Tarver wrote on 2017-06-20:
I tried the .prg route before, but I re-did it based on your
recommendation
just in case I did something wrong.
Here's what I have set up now:
start-vfp9x64.FPW file:
TMPFILES=c:\temp EDITWORK=c:\temp SORTWORK=c:\temp PROGWORK=c:\temp
PATH = .\DATA; .\FORMS; .\GRAPHICS; .\LIBS; .\MENUS; .\PROGRAMS;
.\REPORTS;
T:\LIBRARY
DEFAULT = "T:\ACTIVE\TPM " RESOURCE = "T:\ ACTIVE\TPM \FOXUSER.DBF" COMMAND = do "T:\ ACTIVE\TPM \start-vfp9x64.prg"
start-vfp9x64.prg ************************************************************* CLEAR MEMORY CLOSE DATA CLEAR ALL CLOSE ALL SET SYSMENU TO DEFAULT
CD " T:\ ACTIVE\TPM" MODIFY PROJECT trnslate.pjx NOWAIT ACTIVATE WINDOW COMMAND
When I start VFP from the shortcut, the .FPW is processed and the .PRG is run, the project manager opens with the correct project, a blank command window opens and I cannot type in the command window because every
keystroke
is passed directly to the project manager. Once I close the blank command window, I can open a new command window and everything works normally.
Same
results that I get if I issue the MODIFY PROJECT command directly from
the
.FPW.
Interestingly, if I open VFP in the folder and I type 'do
start-vfp9x64.prg'
in the command window, the project manager opens normally with the
correct
project info and goes immediately back to the regular command window
ready
for my next input. In other words, it looks like the problem may be in
the
.FPW file. So, I went back to the .FPW file and removed everything except the PATH and COMMAND lines. Same result. I also noticed that when I close the blank command window and file named _command.prg is created in the project folder.
This is getting personal now. Uggghhhh.
Paul H. Tarver Tarver Program Consultants, Inc. Email: paul@tpcqpc.com
Tracy,
I think there are a lot of little creature comforts that I can see setting if I can get this process to work correctly. And because I'm automating the creation of those startup files, it is going to save me a lot of time on the multiple projects I go through on an annual basis. However, at this point I'm keeping the code as simple as possible to try and figure out what is going on.
FYI in case those reading this thread, I use Thor and I have tested this with and without Thor as the default startup program. No difference.
Paul H. Tarver Tarver Program Consultants, Inc. Email: paul@tpcqpc.com
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Tracy Pearson Sent: Tuesday, June 20, 2017 11:24 AM To: profoxtech@leafe.com Subject: RE: Modify Project from Config.FPW
Paul,
I use a PRG. I am not seeing the behavior you are talking about.
In my PRG, I do reset the location and widths of the windows I have open. Properties, Document View and DataSession are docked together. Then the Command Window is docked under them. These are all docked to the right side of the screen. I have this because I will occasionally remote in to my computer. The laptop resolution is smaller than the desktop.
Tracy Pearson PowerChurch Software
Paul H. Tarver wrote on 2017-06-20:
I tried the .prg route before, but I re-did it based on your
recommendation
just in case I did something wrong.
Here's what I have set up now:
start-vfp9x64.FPW file:
TMPFILES=c:\temp EDITWORK=c:\temp SORTWORK=c:\temp PROGWORK=c:\temp
PATH = .\DATA; .\FORMS; .\GRAPHICS; .\LIBS; .\MENUS; .\PROGRAMS;
.\REPORTS;
T:\LIBRARY
DEFAULT = "T:\ACTIVE\TPM " RESOURCE = "T:\ ACTIVE\TPM \FOXUSER.DBF" COMMAND = do "T:\ ACTIVE\TPM \start-vfp9x64.prg"
start-vfp9x64.prg ************************************************************* CLEAR MEMORY CLOSE DATA CLEAR ALL CLOSE ALL SET SYSMENU TO DEFAULT
CD " T:\ ACTIVE\TPM" MODIFY PROJECT trnslate.pjx NOWAIT ACTIVATE WINDOW COMMAND
When I start VFP from the shortcut, the .FPW is processed and the .PRG is run, the project manager opens with the correct project, a blank command window opens and I cannot type in the command window because every
keystroke
is passed directly to the project manager. Once I close the blank command window, I can open a new command window and everything works
normally. Same
results that I get if I issue the MODIFY PROJECT command directly from
the
.FPW.
Interestingly, if I open VFP in the folder and I type 'do
start-vfp9x64.prg'
in the command window, the project manager opens normally with the
correct
project info and goes immediately back to the regular command window
ready
for my next input. In other words, it looks like the problem may be in
the
.FPW file. So, I went back to the .FPW file and removed everything except the PATH and COMMAND lines. Same result. I also noticed that when I close the blank command window and file named _command.prg is created in the project folder.
This is getting personal now. Uggghhhh.
Paul H. Tarver Tarver Program Consultants, Inc. Email: paul@tpcqpc.com
[excessive quoting removed by server]
-
Gianni Turri -
Paul H. Tarver -
Ted Roche -
Tracy Pearson