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: [email protected] -----Original Message----- From: ProfoxTech [mailto:[email protected]] On Behalf Of Ted Roche Sent: Monday, June 19, 2017 7:25 PM To: [email protected] Subject: Re: Modify Project from Config.FPW On Mon, Jun 19, 2017 at 7:28 PM, Paul H. Tarver <[email protected]> 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] _______________________________________________ Post Messages to: [email protected] 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/[email protected] ** 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.
