Hi Mike,
Maybe, when compiling the EXE you are not saving tot he project folder? Always (!) save your exe to the project-root folder. Next idea: When calling the form, use the relative pathing to that form: i.e. DO FORM forms\myform.scx
wOOdy
-----Ursprüngliche Nachricht----- Von: ProFox profox-bounces@leafe.com Im Auftrag von MB Software Solutions, LLC Gesendet: Sonntag, 6. Dezember 2020 04:32 An: ProFox Email List profox@leafe.com Betreff: SCX form included in EXE is not found on DO FORM line
VFP9SP2 - Win 7 Pro
43 second demo showing the problem: https://www.screencast.com/t/ZjyWYqFI
The SCX form is included in the EXE. I'm running the EXE. DO FORM <formname> errors saying that the form is not found. Makes no sense to me. Now the app (a legacy app that I inherited which is very dirty) changes the path but still....if the SCX form is included in the EXE, why in the world would it not be found on DO FORM frmMyForm???????
tia, --Mike
-- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
[excessive quoting removed by server]
Hi wOOdy!
You may have the answer: it's definitely NOT the same folder tree...not even the same DRIVE! That makes a difference?!?? I figured it still had the defined form in its saved memory space and would use that!
On 12/7/2020 3:58 AM, Jürgen Wondzinski wrote:
Hi Mike,
Maybe, when compiling the EXE you are not saving tot he project folder? Always (!) save your exe to the project-root folder. Next idea: When calling the form, use the relative pathing to that form: i.e. DO FORM forms\myform.scx
wOOdy
-----Ursprüngliche Nachricht----- Von: ProFox profox-bounces@leafe.com Im Auftrag von MB Software Solutions, LLC Gesendet: Sonntag, 6. Dezember 2020 04:32 An: ProFox Email List profox@leafe.com Betreff: SCX form included in EXE is not found on DO FORM line
VFP9SP2 - Win 7 Pro
43 second demo showing the problem: https://www.screencast.com/t/ZjyWYqFI
The SCX form is included in the EXE. I'm running the EXE. DO FORM <formname> errors saying that the form is not found. Makes no sense to me. Now the app (a legacy app that I inherited which is very dirty) changes the path but still....if the SCX form is included in the EXE, why in the world would it not be found on DO FORM frmMyForm???????
tia, --Mike
-- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
[excessive quoting removed by server]
Is there a SET PATH in your app config?
--
rk
-----Original Message----- From: ProfoxTech profoxtech-bounces@leafe.com On Behalf Of MB Software Solutions, LLC Sent: Monday, December 7, 2020 9:17 AM To: profoxtech@leafe.com Subject: Re: SCX form included in EXE is not found on DO FORM line
Hi wOOdy!
You may have the answer: it's definitely NOT the same folder tree...not even the same DRIVE! That makes a difference?!?? I figured it still had the defined form in its saved memory space and would use that!
On 12/7/2020 3:58 AM, Jürgen Wondzinski wrote:
Hi Mike,
Maybe, when compiling the EXE you are not saving tot he project folder? Always (!) save your exe to the project-root folder. Next idea: When calling the form, use the relative pathing to that form: i.e. DO FORM forms\myform.scx
wOOdy
-----Ursprüngliche Nachricht----- Von: ProFox profox-bounces@leafe.com Im Auftrag von MB Software Solutions, LLC Gesendet: Sonntag, 6. Dezember 2020 04:32 An: ProFox Email List profox@leafe.com Betreff: SCX form included in EXE is not found on DO FORM line
VFP9SP2 - Win 7 Pro
43 second demo showing the problem: https://www.screencast.com/t/ZjyWYqFI
The SCX form is included in the EXE. I'm running the EXE. DO FORM <formname> errors saying that the form is not found. Makes no sense to me. Now the app (a legacy app that I inherited which is very dirty) changes the path but still....if the SCX form is included in the EXE, why in the world would it not be found on DO FORM frmMyForm???????
tia, --Mike
-- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
[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/13dc0d04-0360-aa98-e732-1b0e29e51a5a@mbsoft... ** 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. Report [OT] Abuse: http://leafe.com/reportAbuse/13dc0d04-0360-aa98-e732-1b0e29e51a5a@mbsoftware...
Mike,
Now that I reflect again on this. Here's a little story.
I was setting up a build machine. Pulls code from Source Control, and builds the project. This build machine was putting the project on the larger D: and running the compile there. A customer with a new laptop that did not have a D: could not run the application because it could not find the D:. The error may have been a file not found error. It has been years. The project lives on the C: drive. The EXE when built goes into a different tree on the C: drive. I don't have this type of error. I see all the forms in the project live in the root with the pjx.
Here's another thing that has happened to customers. The EXE was being run from a network drive. The user walks away from the computer for 20 or so minutes. When they return they get an error about a file missing. The network connection went to sleep. VFP tried to read a file in the EXE and it wasn't available. The error is about a missing form or classlib.
HTH, Tracy
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Richard Kaye Sent: Monday, December 07, 2020 9:38 AM To: profoxtech@leafe.com Subject: RE: SCX form included in EXE is not found on DO FORM line
Is there a SET PATH in your app config?
--
rk
-----Original Message----- From: ProfoxTech profoxtech-bounces@leafe.com On Behalf Of MB Software Solutions, LLC Sent: Monday, December 7, 2020 9:17 AM To: profoxtech@leafe.com Subject: Re: SCX form included in EXE is not found on DO FORM line
Hi wOOdy!
You may have the answer: it's definitely NOT the same folder tree...not even the same DRIVE! That makes a difference?!?? I figured it still had the defined form in its saved memory space and would use that!
On 12/7/2020 3:58 AM, Jürgen Wondzinski wrote:
Hi Mike,
Maybe, when compiling the EXE you are not saving tot he project folder? Always (!) save your exe to the project-root folder. Next idea: When calling the form, use the relative pathing to that form: i.e. DO FORM forms\myform.scx
wOOdy
-----Ursprüngliche Nachricht----- Von: ProFox profox-bounces@leafe.com Im Auftrag von MB Software Solutions, LLC Gesendet: Sonntag, 6. Dezember 2020 04:32 An: ProFox Email List profox@leafe.com Betreff: SCX form included in EXE is not found on DO FORM line
VFP9SP2 - Win 7 Pro
43 second demo showing the problem: https://www.screencast.com/t/ZjyWYqFI
The SCX form is included in the EXE. I'm running the EXE. DO FORM <formname> errors saying that the form is not found. Makes no sense to me. Now the app (a legacy app that I inherited which is very dirty) changes the path but still....if the SCX form is included in the EXE, why in the world would it not be found on DO FORM frmMyForm???????
tia, --Mike
-- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
[excessive quoting removed by server]
Hi Tracy,
Those wouldn't apply to me here because this is all done on my Dev machine (dev and testing). Legacy core project files are on c:\wsapps\bwd but my MBSS additions come from e:\dev\client....
Again, the strange thing is that this works AT THE CLIENT SITE where my e:\dev folder doesn't exist at all.
On 12/7/2020 9:53 AM, Tracy Pearson wrote:
Mike,
Now that I reflect again on this. Here's a little story.
I was setting up a build machine. Pulls code from Source Control, and builds the project. This build machine was putting the project on the larger D: and running the compile there. A customer with a new laptop that did not have a D: could not run the application because it could not find the D:. The error may have been a file not found error. It has been years. The project lives on the C: drive. The EXE when built goes into a different tree on the C: drive. I don't have this type of error. I see all the forms in the project live in the root with the pjx.
Here's another thing that has happened to customers. The EXE was being run from a network drive. The user walks away from the computer for 20 or so minutes. When they return they get an error about a file missing. The network connection went to sleep. VFP tried to read a file in the EXE and it wasn't available. The error is about a missing form or classlib.
HTH, Tracy
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Richard Kaye Sent: Monday, December 07, 2020 9:38 AM To: profoxtech@leafe.com Subject: RE: SCX form included in EXE is not found on DO FORM line
Is there a SET PATH in your app config?
--
rk
-----Original Message----- From: ProfoxTech profoxtech-bounces@leafe.com On Behalf Of MB Software Solutions, LLC Sent: Monday, December 7, 2020 9:17 AM To: profoxtech@leafe.com Subject: Re: SCX form included in EXE is not found on DO FORM line
Hi wOOdy!
You may have the answer: it's definitely NOT the same folder tree...not even the same DRIVE! That makes a difference?!?? I figured it still had the defined form in its saved memory space and would use that!
On 12/7/2020 3:58 AM, Jürgen Wondzinski wrote:
Hi Mike,
Maybe, when compiling the EXE you are not saving tot he project folder? Always (!) save your exe to the project-root folder. Next idea: When calling the form, use the relative pathing to that form: i.e. DO FORM forms\myform.scx
wOOdy
-----Ursprüngliche Nachricht----- Von: ProFox profox-bounces@leafe.com Im Auftrag von MB Software Solutions, LLC Gesendet: Sonntag, 6. Dezember 2020 04:32 An: ProFox Email List profox@leafe.com Betreff: SCX form included in EXE is not found on DO FORM line
VFP9SP2 - Win 7 Pro
43 second demo showing the problem: https://www.screencast.com/t/ZjyWYqFI
The SCX form is included in the EXE. I'm running the EXE. DO FORM <formname> errors saying that the form is not found. Makes no sense to me. Now the app (a legacy app that I inherited which is very dirty) changes the path but still....if the SCX form is included in the EXE, why in the world would it not be found on DO FORM frmMyForm???????
tia, --Mike
-- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
[excessive quoting removed by server]
Smells like a PATH issue in your dev environment to me.
--
rk
-----Original Message----- From: ProfoxTech profoxtech-bounces@leafe.com On Behalf Of MB Software Solutions, LLC Sent: Monday, December 7, 2020 2:01 PM To: profoxtech@leafe.com Subject: Re: SCX form included in EXE is not found on DO FORM line
Hi Tracy,
Those wouldn't apply to me here because this is all done on my Dev machine (dev and testing). Legacy core project files are on c:\wsapps\bwd but my MBSS additions come from e:\dev\client....
Again, the strange thing is that this works AT THE CLIENT SITE where my e:\dev folder doesn't exist at all.
Agreed, but why should it matter since the form was INCLUDED in the EXE? I figured "all definitions are in memory" so it should be able to find it no matter what.
On 12/7/2020 2:34 PM, Richard Kaye wrote:
Smells like a PATH issue in your dev environment to me.
--
rk
-----Original Message----- From: ProfoxTech profoxtech-bounces@leafe.com On Behalf Of MB Software Solutions, LLC Sent: Monday, December 7, 2020 2:01 PM To: profoxtech@leafe.com Subject: Re: SCX form included in EXE is not found on DO FORM line
Hi Tracy,
Those wouldn't apply to me here because this is all done on my Dev machine (dev and testing). Legacy core project files are on c:\wsapps\bwd but my MBSS additions come from e:\dev\client....
Again, the strange thing is that this works AT THE CLIENT SITE where my e:\dev folder doesn't exist at all.
[excessive quoting removed by server]
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.
--
rk
-----Original Message----- From: ProfoxTech profoxtech-bounces@leafe.com On Behalf Of MB Software Solutions, LLC Sent: Monday, December 7, 2020 10:07 PM To: profoxtech@leafe.com Subject: Re: SCX form included in EXE is not found on DO FORM line
Agreed, but why should it matter since the form was INCLUDED in the EXE? I figured "all definitions are in memory" so it should be able to find it no matter what.
On 12/7/2020 2:34 PM, Richard Kaye wrote:
Smells like a PATH issue in your dev environment to me.
--
rk
-----Original Message----- From: ProfoxTech profoxtech-bounces@leafe.com On Behalf Of MB Software Solutions, LLC Sent: Monday, December 7, 2020 2:01 PM To: profoxtech@leafe.com Subject: Re: SCX form included in EXE is not found on DO FORM line
Hi Tracy,
Those wouldn't apply to me here because this is all done on my Dev machine (dev and testing). Legacy core project files are on c:\wsapps\bwd but my MBSS additions come from e:\dev\client....
Again, the strange thing is that this works AT THE CLIENT SITE where my e:\dev folder doesn't exist at all.
[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/5c505b6c-dfd1-804e-d6e8-e5967a75fc50@mbsoft... ** 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. Report [OT] Abuse: http://leafe.com/reportAbuse/5c505b6c-dfd1-804e-d6e8-e5967a75fc50@mbsoftware...
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
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
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:
- Your exe calls an SCX (DO MyForm.scx - without any path to the scx
in the call)
The SCX is included in the exe
When the exe runs at your client site or on your PC outside of the
VFP IDE the form is run properly
- 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.
- 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]
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:
- Your exe calls an SCX (DO MyForm.scx - without any path to the scx
in the call)
The SCX is included in the exe
When the exe runs at your client site or on your PC outside of the
VFP IDE the form is run properly
- 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.
- 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]
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:
- Your exe calls an SCX (DO MyForm.scx - without any path to the
scx in the call)
The SCX is included in the exe
When the exe runs at your client site or on your PC outside of
the VFP IDE the form is run properly
- 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.
- 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]
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" mbsoftwaresolutions@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:
- Your exe calls an SCX (DO MyForm.scx - without any path to the
scx in the call)
The SCX is included in the exe
When the exe runs at your client site or on your PC outside of
the VFP IDE the form is run properly
- 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.
- 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]
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" mbsoftwaresolutions@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:
- Your exe calls an SCX (DO MyForm.scx - without any path to the
scx in the call)
The SCX is included in the exe
When the exe runs at your client site or on your PC outside of
the VFP IDE the form is run properly
- 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.
- 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]
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 your dev classes into another folder on the same drive (does not have to be under the same project folder, can be a totally unrelated one) and see if that works. (or you could move the project onto the same drive as your dev classes.)
Frank.
Frank Cazabon
On 09/12/2020 10:14 am, MB Software Solutions, LLC wrote:
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" mbsoftwaresolutions@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:
- Your exe calls an SCX (DO MyForm.scx - without any path to the
scx in the call)
The SCX is included in the exe
When the exe runs at your client site or on your PC outside of
the VFP IDE the form is run properly
- 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.
- 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]
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: consultant@srikanthbhandari.ind.in / srikanth.bhandaari@gmail.com Web: srikanthbhandari.ind.in
On Tue, Dec 8, 2020 at 1:17 PM MB Software Solutions, LLC < mbsoftwaresolutions@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:
- Your exe calls an SCX (DO MyForm.scx - without any path to the
scx in the call)
The SCX is included in the exe
When the exe runs at your client site or on your PC outside of
the VFP IDE the form is run properly
- 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.
- 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]
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: consultant@srikanthbhandari.ind.in / srikanth.bhandaari@gmail.com Web: srikanthbhandari.ind.in
On Tue, Dec 8, 2020 at 1:17 PM MB Software Solutions, LLC < mbsoftwaresolutions@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:
- Your exe calls an SCX (DO MyForm.scx - without any path to the
scx in the call)
The SCX is included in the exe
When the exe runs at your client site or on your PC outside of
the VFP IDE the form is run properly
- 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.
- 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]
It could be the form location on a different drive/volume is the source of your fun...
--
rk
-----Original Message----- From: ProfoxTech profoxtech-bounces@leafe.com On Behalf Of MB Software Solutions, LLC Sent: Wednesday, December 9, 2020 9:17 AM To: profoxtech@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: consultant@srikanthbhandari.ind.in / srikanth.bhandaari@gmail.com Web: srikanthbhandari.ind.in
On Tue, Dec 8, 2020 at 1:17 PM MB Software Solutions, LLC < mbsoftwaresolutions@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:
- Your exe calls an SCX (DO MyForm.scx - without any path to the
scx in the call)
The SCX is included in the exe
When the exe runs at your client site or on your PC outside of
the VFP IDE the form is run properly
- 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.
- 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/5325090d-e131-609d-f495-2e5f9ba22df3@mbsoft... ** 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. Report [OT] Abuse: http://leafe.com/reportAbuse/5325090d-e131-609d-f495-2e5f9ba22df3@mbsoftware...
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-bounces@leafe.com On Behalf Of MB Software Solutions, LLC Sent: Wednesday, December 9, 2020 9:17 AM To: profoxtech@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: consultant@srikanthbhandari.ind.in / srikanth.bhandaari@gmail.com Web: srikanthbhandari.ind.in
On Tue, Dec 8, 2020 at 1:17 PM MB Software Solutions, LLC < mbsoftwaresolutions@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:
- Your exe calls an SCX (DO MyForm.scx - without any path to the
scx in the call)
The SCX is included in the exe
When the exe runs at your client site or on your PC outside of
the VFP IDE the form is run properly
- 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.
- 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]
Try adding a config.fpw with the dev path on your dev system?
--
rk
-----Original Message----- From: ProfoxTech profoxtech-bounces@leafe.com On Behalf Of MB Software Solutions, LLC Sent: Wednesday, December 9, 2020 9:51 AM To: profoxtech@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-bounces@leafe.com On Behalf Of MB Software Solutions, LLC Sent: Wednesday, December 9, 2020 9:17 AM To: profoxtech@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: consultant@srikanthbhandari.ind.in / srikanth.bhandaari@gmail.com Web: srikanthbhandari.ind.in
On Tue, Dec 8, 2020 at 1:17 PM MB Software Solutions, LLC < mbsoftwaresolutions@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:
- Your exe calls an SCX (DO MyForm.scx - without any path to the
scx in the call)
The SCX is included in the exe
When the exe runs at your client site or on your PC outside of
the VFP IDE the form is run properly
- 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.
- 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/9da15e07-7e1d-cfb7-c868-43e463a93ddd@mbsoft... ** 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. Report [OT] Abuse: http://leafe.com/reportAbuse/9da15e07-7e1d-cfb7-c868-43e463a93ddd@mbsoftware...
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-bounces@leafe.com On Behalf Of MB Software Solutions, LLC Sent: Wednesday, December 9, 2020 9:51 AM To: profoxtech@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-bounces@leafe.com On Behalf Of MB Software Solutions, LLC Sent: Wednesday, December 9, 2020 9:17 AM To: profoxtech@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: consultant@srikanthbhandari.ind.in / srikanth.bhandaari@gmail.com Web: srikanthbhandari.ind.in
On Tue, Dec 8, 2020 at 1:17 PM MB Software Solutions, LLC < mbsoftwaresolutions@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]
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. What are the values for SET DEFAULT and SET PATH?
--
rk
-----Original Message----- From: ProfoxTech profoxtech-bounces@leafe.com On Behalf Of MB Software Solutions, LLC Sent: Wednesday, December 9, 2020 12:09 PM To: profoxtech@leafe.com Subject: Re: SCX form included in EXE is not found on DO FORM line
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-bounces@leafe.com On Behalf Of MB Software Solutions, LLC Sent: Wednesday, December 9, 2020 9:51 AM To: profoxtech@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-bounces@leafe.com On Behalf Of MB Software Solutions, LLC Sent: Wednesday, December 9, 2020 9:17 AM To: profoxtech@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: consultant@srikanthbhandari.ind.in / srikanth.bhandaari@gmail.com Web: srikanthbhandari.ind.in
On Tue, Dec 8, 2020 at 1:17 PM MB Software Solutions, LLC < mbsoftwaresolutions@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/05908934-27ec-0de1-cf94-42c4b4613b11@mbsoft... ** 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. Report [OT] Abuse: http://leafe.com/reportAbuse/05908934-27ec-0de1-cf94-42c4b4613b11@mbsoftware...
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 would run for sure. Which means you create a new Project for the SCX & generate an Exe. You might end up with Newer challenges 😁 unless the SCX can run independently.
-- Cheers!!!
*Srikanth Bhandari* Mobile: +91 99625 42134 / +91 99001 39393 Email: consultant@srikanthbhandari.ind.in / srikanth.bhandaari@gmail.com Web: srikanthbhandari.ind.in
On Wed, Dec 9, 2020 at 10:50 AM Richard Kaye rkaye@invaluable.com wrote:
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. What are the values for SET DEFAULT and SET PATH?
--
rk
-----Original Message----- From: ProfoxTech profoxtech-bounces@leafe.com On Behalf Of MB Software Solutions, LLC Sent: Wednesday, December 9, 2020 12:09 PM To: profoxtech@leafe.com Subject: Re: SCX form included in EXE is not found on DO FORM line
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-bounces@leafe.com On Behalf Of MB Software Solutions, LLC Sent: Wednesday, December 9, 2020 9:51 AM To: profoxtech@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-bounces@leafe.com On Behalf Of MB Software Solutions, LLC Sent: Wednesday, December 9, 2020 9:17 AM To: profoxtech@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: consultant@srikanthbhandari.ind.in / srikanth.bhandaari@gmail.com Web: srikanthbhandari.ind.in
On Tue, Dec 8, 2020 at 1:17 PM MB Software Solutions, LLC < mbsoftwaresolutions@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]
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 the smoking gun.
Thanks all. I just would have lost money believing that because it was included in the EXE, it should be in memory and thus able to be found, especially since we usually always say DO FORM frmCrap instead of DO FORM \forms\frmCrap. (Or at least I do. I stopped putting paths in code years ago for included forms because I got an error by a form that was NOT included in the EXE and didn't ship separately and thus failed to open when called from the app.
On 12/9/2020 1:49 PM, Richard Kaye wrote:
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. What are the values for SET DEFAULT and SET PATH?
--
rk
-----Original Message----- From: ProfoxTech profoxtech-bounces@leafe.com On Behalf Of MB Software Solutions, LLC Sent: Wednesday, December 9, 2020 12:09 PM To: profoxtech@leafe.com Subject: Re: SCX form included in EXE is not found on DO FORM line
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-bounces@leafe.com On Behalf Of MB Software Solutions, LLC Sent: Wednesday, December 9, 2020 9:51 AM To: profoxtech@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-bounces@leafe.com On Behalf Of MB Software Solutions, LLC Sent: Wednesday, December 9, 2020 9:17 AM To: profoxtech@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: consultant@srikanthbhandari.ind.in / srikanth.bhandaari@gmail.com Web: srikanthbhandari.ind.in
On Tue, Dec 8, 2020 at 1:17 PM MB Software Solutions, LLC < mbsoftwaresolutions@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]
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-bounces@leafe.com On Behalf Of MB Software Solutions, LLC Sent: Wednesday, December 9, 2020 9:51 AM To: profoxtech@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-bounces@leafe.com On Behalf Of MB Software Solutions, LLC Sent: Wednesday, December 9, 2020 9:17 AM To: profoxtech@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: consultant@srikanthbhandari.ind.in / srikanth.bhandaari@gmail.com Web: srikanthbhandari.ind.in
On Tue, Dec 8, 2020 at 1:17 PM MB Software Solutions, LLC < mbsoftwaresolutions@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]
FYI, the movie was better than the book. :)
Paul H. Tarver Tarver Program Consultants, Inc.
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Richard Kaye Sent: Tuesday, December 08, 2020 8:22 AM To: profoxtech@leafe.com Subject: RE: SCX form included in EXE is not found on DO FORM line
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.
--
rk
-----Original Message----- From: ProfoxTech profoxtech-bounces@leafe.com On Behalf Of MB Software Solutions, LLC Sent: Monday, December 7, 2020 10:07 PM To: profoxtech@leafe.com Subject: Re: SCX form included in EXE is not found on DO FORM line
Agreed, but why should it matter since the form was INCLUDED in the EXE? I figured "all definitions are in memory" so it should be able to find it no matter what.
On 12/7/2020 2:34 PM, Richard Kaye wrote:
Smells like a PATH issue in your dev environment to me.
--
rk
-----Original Message----- From: ProfoxTech profoxtech-bounces@leafe.com On Behalf Of MB Software Solutions, LLC Sent: Monday, December 7, 2020 2:01 PM To: profoxtech@leafe.com Subject: Re: SCX form included in EXE is not found on DO FORM line
Hi Tracy,
Those wouldn't apply to me here because this is all done on my Dev machine (dev and testing). Legacy core project files are on c:\wsapps\bwd but my MBSS additions come from e:\dev\client....
Again, the strange thing is that this works AT THE CLIENT SITE where my e:\dev folder doesn't exist at all.
[excessive quoting removed by server]
I know, right! If only folks wasted 43-seconds instead of all this book reading. :D
On 12/8/2020 12:50 PM, Paul H. Tarver wrote:
FYI, the movie was better than the book. :)
Paul H. Tarver Tarver Program Consultants, Inc.
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Richard Kaye Sent: Tuesday, December 08, 2020 8:22 AM To: profoxtech@leafe.com Subject: RE: SCX form included in EXE is not found on DO FORM line
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.
--
rk
-----Original Message----- From: ProfoxTech profoxtech-bounces@leafe.com On Behalf Of MB Software Solutions, LLC Sent: Monday, December 7, 2020 10:07 PM To: profoxtech@leafe.com Subject: Re: SCX form included in EXE is not found on DO FORM line
Agreed, but why should it matter since the form was INCLUDED in the EXE? I figured "all definitions are in memory" so it should be able to find it no matter what.
On 12/7/2020 2:34 PM, Richard Kaye wrote:
Smells like a PATH issue in your dev environment to me.
--
rk
-----Original Message----- From: ProfoxTech profoxtech-bounces@leafe.com On Behalf Of MB Software Solutions, LLC Sent: Monday, December 7, 2020 2:01 PM To: profoxtech@leafe.com Subject: Re: SCX form included in EXE is not found on DO FORM line
Hi Tracy,
Those wouldn't apply to me here because this is all done on my Dev machine (dev and testing). Legacy core project files are on c:\wsapps\bwd but my MBSS additions come from e:\dev\client....
Again, the strange thing is that this works AT THE CLIENT SITE where my e:\dev folder doesn't exist at all.
[excessive quoting removed by server]