Ed & company:

I got Koen's reply, but never saw Tracy's original message. Often when
this happens the original is in the Spam folder, but not this morning.

Just thought I'd flag this as Ed had said he was moving around some
domains and this might be a sign of trouble. Hope not.


---------- Forwarded message ----------
From: Koen Piller <[email protected]>
Date: Thu, Jan 7, 2016 at 11:23 AM
Subject: Re: VFP 9.00.0000.5815 and a bad PATH environment variable
To: [email protected]


Hi,
You did not mention which OS() and where the by you constructed myVFP.exe
resides.
By the way, any reason for not installing the hotfixes?
https://www.berezniker.com/content/pages/visual-foxpro/vfp-90-versions

Regards,
Koen



2016-01-07 15:30 GMT+01:00 Tracy Pearson <[email protected]>:

> Hello everyone,
>
> I have been getting a steady one or two calls a month for a year about our
> VFP 9 program not starting and getting the following dialog:
>
>     ----------------------------------------
>     Program Error
>     ----------------------------------------
>     Invalid path or file name.
>     ----------------------------------------
>     Cancel     Ignore     Help
>     ----------------------------------------
>
> I have placed in the CONFIG.FPW the following
>     COVERAGE=STARTUPCOVERAGE.TXT
>
> When I start the program with an invalid PATH environment variable, the
> coverage file is created. However it is 0 bytes.
>
> I created a test project.
> It contains a MAIN.PRG
>     ON SHUTDOWN clear events
>     READ EVENTS
>     ON SHUTDOWN
>
> It also contains a CONFIG.FPW
>     title=Bad Path Testing
>     resource=off
>
> When this project starts without the bad PATH environment variable it opens
> and closes without problems.
> I start a CMD prompt and run the following line to break the PATH
> environment variable
>     PATH=%PATH%:c:\windows
>
> (yes, the : separating the path instead of a semicolon is a common problem
> I've been seeing)
>
> Start the EXE from this now corrupted environment CMD window and the error
> will happen.
> This wasn't a problem with VFP 9.00.0000.3504
> I do update the manifest in my VFP 9.00.0000.3504, which does start causing
> the problem.
>
> Does anyone have some thoughts or ideas as to what might be the problem?
>
> Thank you,
> Tracy
>
>
>
[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/cacw6n4sw__8ptesdtq2kc-08wswpy-oxc2n6ovcugm54z_1...@mail.gmail.com
** 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.

Reply via email to