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 least not intentionally). For
example, if you do have a SET PATH command or config somewhere it will
always search that first, even if the resource was included in the .exe.
Then, as a second quirk, I seem to recall that when calling a form (or a
classlib, or a report) if a search for 'something' was started, and
just 'one thing' is found, VFP assumes everything else is there too.
And that will start generating 'not found' dialogs.
Also, if I recall correctly, you can actually run an '.exe' file inside
the VFP IDE (is that kind of how the debugger works with .exes?) - I may
be off on that. But maybe if you're doing the 'run after build' you are
not actually running it 'independent' of the IDE environment (which
probably has pathing set, etc).
Anyway, I do remember quirks, and the process I switched to was this:
1) of course, remove any 'set path' commands/config, etc - if paths are
important I 'calculate' and put in a variable when the .exe starts up
(e.g. to open a database in a subfolder, etc)
2) create a separate folder - like under a 'test' folder on my dev machine.
3) treat that folder as my 'production test' site (thus if there are
other files/subfolders to set up, get them set up as well)
4) compile to exe, then copy the exe from the project folder (where the
.pjx file was) to my 'production test' folder
5) run the exe from Total Commander (or any File manager like Windows
Explorer)
I little bit of a pain I know, but that helped me avoid all kinds of
little issues and better emulate what would happen on target machines.
-Charlie
On 12/9/2020 12:08 PM, MB Software Solutions, LLC wrote:
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 Message-----
From: ProfoxTech <profoxtech-boun...@leafe.com> 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....wOOdy 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...
--
rk
-----Original Message-----
From: ProfoxTech <profoxtech-boun...@leafe.com> 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 found on DO FORM line
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 possible as it has proven fragile/unsteady in the past years.
On 12/9/2020 3:47 AM, Srikanth Bhandari wrote:
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
for better organizing put them in, as many, Sub-Folders within the
Project Folder.
I am sure doing the above would solve your challenge.
--
Cheers!!!
*Srikanth Bhandari*
Mobile: +1 669 292 9849 / +91 99625 42134 / +91 99001 39393
Email: consult...@srikanthbhandari.ind.in /
srikanth.bhanda...@gmail.com
Web: srikanthbhandari.ind.in
On Tue, Dec 8, 2020 at 1:17 PM MB Software Solutions, LLC <
mbsoftwaresoluti...@mbsoftwaresolutions.com> wrote:
Oh sorry, Frank. Let me clarify:
Project is in on my C: drive in the legacy folder (c:\wsapps\bwd).
Form is in E: drive in my Dev\Client\Forms folder.
Clear as mud now? ;-)
--Mike
On 12/8/2020 2:23 PM, Frank Cazabon wrote:
I had looked at it 2 or 3 times but it doesn't answer some of the
questions asked by others here and I'm still not 100% sure of one
thing in particular.
Woody asked you:
Maybe, when compiling the EXE you are not saving tot he project
folder?
and you responded:
it's definitely NOT the same folder tree...not even the same DRIVE!
but below you have confirmed that point #5 is correct that it was
built in the same folder as the PJX.
Which is it?
Frank.
Frank Cazabon
On 08/12/2020 3:07 pm, MB Software Solutions, LLC wrote:
Hi Frank,
Yeah...pretty much right. Take 43 seconds and see what I mean:
43 second demo showing the problem:
https://www.screencast.com/t/ZjyWYqFI
On 12/8/2020 12:22 PM, Frank Cazabon wrote:
Mike,
I'm coming in a bit late and am a bit unclear on some of your
answers to previous questions. Let me know if this summary is
accurate or not, please:
1. Your exe calls an SCX (DO MyForm.scx - without any path to the
scx in the call)
2. The SCX is included in the exe
3. When the exe runs at your client site or on your PC outside of
the VFP IDE the form is run properly
4. When you run the exe within the VFP IDE on your PC it fails,
unless you have a SET PATH to the folder where the SCX is.
5. Your PJX and the EXE are both in the same folder on your
development PC (the exe is actually built there, not built
elsewhere and copied back)
Frank.
Frank Cazabon
On 08/12/2020 1:03 pm, MB Software Solutions, LLC wrote:
On 12/8/2020 9:22 AM, Richard Kaye wrote:
A fine question. 😊
I didn't watch the movie. Are you putting a path in on your DO
FORM call? Do you have a back door where you can see the
runtime environment settings? I would think if you want VFP to
walk its path to find the form in the EXE, then your DO FORM
call should not include a fully qualified path or even a
partial one.
Exactly....when I remove the pathing, it fails on my Dev machine
(even when run inside the VFP IDE as I do the "run after build"
option when creating the EXE). I have to put the pathing there
for it to work. BUT, WHEN DEPLOYED TO THE CLIENT, WHERE THAT
DEV FOLDER DOESN'T EXIST, it works.
Cue Randy Quaid in the Vacation movies saying "I don't know!" :D
[excessive quoting removed by server]
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: https://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: https://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: https://leafe.com/archives
This message:
https://leafe.com/archives/byMID/58b21619-00ef-fbbd-8cbd-f36409dd3...@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.
