Hi Mike,
My guess is that the SCX should
- either be in the same folder as the Project
- or in a sub-folder of the Project folder
If it is in any other location it would run in Runtime but would fail while
running in the EXE.
Recommended that all Project Files be kept in the Project Folder or fo
Yes. EXE is created in the default location, same as the Project files.
On 12/8/2020 4:38 PM, Frank Cazabon wrote:
But when you compile the exe, does that get created in the same place as the
pjx/t?
On 8 December 2020 17:17:07 GMT-04:00, "MB Software Solutions, LLC"
wrote:
Oh sorry, Frank.
Hi Srikanth,
I agree with you on better project management, and I always do that for
my own projects, but with this inherited one (that's a real pain in the
arse), I tried to change as little as possible. My approach with this
project has always been to take the "least invasive" approach possi
It could be the form location on a different drive/volume is the source of your
fun...
--
rk
-Original Message-
From: ProfoxTech On Behalf Of MB Software
Solutions, LLC
Sent: Wednesday, December 9, 2020 9:17 AM
To: profoxt...@leafe.com
Subject: Re: SCX form included in EXE is not fou
YeahwOOdy posited that too. I'm guessing that's the cause...but
weird that it works in the Production (client) server space but just not
on my dev machine.
On 12/9/2020 9:29 AM, Richard Kaye wrote:
It could be the form location on a different drive/volume is the source of your
fun...
--
Try adding a config.fpw with the dev path on your dev system?
--
rk
-Original Message-
From: ProfoxTech On Behalf Of MB Software
Solutions, LLC
Sent: Wednesday, December 9, 2020 9:51 AM
To: profoxt...@leafe.com
Subject: Re: SCX form included in EXE is not found on DO FORM line
Yeah...
Can we agree though that if a SCX form is included in your EXE, a DO
FORM frmCrap should work regardless of its pathing??? That's what blows
my mind on this one.
On 12/9/2020 9:55 AM, Richard Kaye wrote:
Try adding a config.fpw with the dev path on your dev system?
--
rk
-Original Mes
OK. A couple things I would try:
1. After building the exe, try to run the exe in a separate instance of
the IDE and see if that works.
2. Try running a form based on VFP's base form class with only VFP base
class objects on it that is in the same folder as the trouble form.
3. Try moving y
Nope. Can't do it. 😊
VFP does funny stuff with relative pathing in SCX/VCX/MNX for image refs and
include files. I think VFP is looking on the C drive for that form and unless
you explicitly add the path to the forms folder on the E drive, it's not going
to find it.
I just watched the movie.
My experience is that if the dependent files are outside the Project Root
Folder they would run in a Development Environment but would not in another
environment.
However if you compile the SCX as a separate EXE & try running an external
EXE from within your project (the SCX EXE in this case) it w
Screenshot: https://www.screencast.com/t/xcxxlUanhv
SET PATH looks like a bastard (incorrect) expression value, data folder,
app startup folder, and WWWC website folder.
("FULLPATH(CURDIR()),\WSDATA\BW2005,\WSAPPS\BW2005,\WEBSITES\BW2005")
SET DEFA is just the C: drive
I'm betting that's
I haven't kept up with all the messages, so I apologize if the following
has been covered - just ignore if that's the case.
My recollection is VFP is pretty strange about the 'pathing' - and I
agree that using SET PATH is an undesirable thing (and I think you
mentioned you're not using it - at
12 matches
Mail list logo