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]