Author: mbsoftwaresolutions@mbsoftwaresolutions.com
Posted: 2017-07-27 10:20:47 Link
VFP9SP2
Frustrated!!! All of the sudden my 2003 project code wants to rebel.
I'm trying to debug some things and when I try to step into the
code--code which has worked since 2003, mind you--it now says "Source
not available" DESPITE THE FACT that I'm in the Project's home folder,
where the EXE resides (I did a Build EXE & Run after), and the PROGS
subfolder is in my path.
Here's my first call to create the Custom biz obj:
https://www.screencast.com/t/5UsbNGGXBGr
Then here's the next screenshot, showing that nasty message and
confirming my curdir() and SET('Path'):
https://www.screencast.com/t/E1UOoe9h
You can see in the first that I've even changed the pathing of the
object call to what it really is. I never do that; I always used
relative pathing like this: NEWOBJECT("Class",".\progs\_bizobj.prg")
I searched the ProFox archives and saw this thread:
https://leafe.com/archives/full_thread/468343 ...but Kurt's issue was
resolved by relocating the EXE to the proper path. Mine is in the same
spot it has been for 14 years! As Sytze (RIP) suggested, I deleted all
of the FXP and did a COMPILE c:\dev\fabmate11\progs\*.prg to recreate
all of them. Using Richard's tip, I verified that yes indeed, my
project does have Debug Info included/checked in the Project manager.
Also reviewed this thread, started by Richard:
https://leafe.com/archives/full_thread/392144. I renamed the EXE and
ran the new one....nope, same bad behavior.
So I've ruled out pathing, out-of-sync FXPs, and the Hale-Bopp comet.
I'm thinking my next step is to recreate the project file from scratch
and rebuild.
Any other ideas?
tia,
--Mike
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/f70ac836b429a21858b1cff4f8fae675@mbsoftwaresolutions.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.
Author: Tracy Pearson
Posted: 2017-07-27 10:36:31 Link
Here's a couple more things to check:
NTFS permissions
Hidden attributes
Also, you can use this in the debugger Watch window:
FULLPATH(".")
-----Original Message-----
From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of
mbsoftwaresolutions@mbsoftwaresolutions.com
Sent: Thursday, July 27, 2017 11:21 AM
To: profoxtech@leafe.com
Subject: "Source not available" -- seems to happen in the history of the
list!
VFP9SP2
Frustrated!!! All of the sudden my 2003 project code wants to rebel.
I'm trying to debug some things and when I try to step into the
code--code which has worked since 2003, mind you--it now says "Source
not available" DESPITE THE FACT that I'm in the Project's home folder,
where the EXE resides (I did a Build EXE & Run after), and the PROGS
subfolder is in my path.
Here's my first call to create the Custom biz obj:
https://www.screencast.com/t/5UsbNGGXBGr
Then here's the next screenshot, showing that nasty message and
confirming my curdir() and SET('Path'):
https://www.screencast.com/t/E1UOoe9h
You can see in the first that I've even changed the pathing of the
object call to what it really is. I never do that; I always used
relative pathing like this: NEWOBJECT("Class",".\progs\_bizobj.prg")
I searched the ProFox archives and saw this thread:
https://leafe.com/archives/full_thread/468343 ...but Kurt's issue was
resolved by relocating the EXE to the proper path. Mine is in the same
spot it has been for 14 years! As Sytze (RIP) suggested, I deleted all
of the FXP and did a COMPILE c:\dev\fabmate11\progs\*.prg to recreate
all of them. Using Richard's tip, I verified that yes indeed, my
project does have Debug Info included/checked in the Project manager.
Also reviewed this thread, started by Richard:
https://leafe.com/archives/full_thread/392144. I renamed the EXE and
ran the new one....nope, same bad behavior.
So I've ruled out pathing, out-of-sync FXPs, and the Hale-Bopp comet.
I'm thinking my next step is to recreate the project file from scratch
and rebuild.
Any other ideas?
tia,
--Mike
[excessive quoting removed by server]
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/000c01d306ee$1f540720$5dfc1560$@powerchurch.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.
Author: Alan Bourke
Posted: 2017-07-27 10:38:48 Link
I get similar issues sometimes. It's always paths or old FXP files
without debug info in them.
Are the PRG files built into the EXE via the project ?
Do you have 'set classlib to progs\_bizobj.prg additive' somewhere at
the setup of your application? I find it's best to be explicit rather
than relying on search paths to find it.
Have you tried building an APP instead of an EXE and running that in
VFP?
--
Alan Bourke
alanpbourke (at) fastmail (dot) fm
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/1501169928.1966264.1054563944.605013B3@webmail.messagingengine.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.
Author: Alan Bourke
Posted: 2017-07-27 10:39:34 Link
Sorry - where I said
'set classlib to progs\_bizobj.prg additive'
I meant
'set procedure to progs\_bizobj.prg additive'
--
Alan Bourke
alanpbourke (at) fastmail (dot) fm
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/1501169974.1966331.1054570400.357015EF@webmail.messagingengine.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.
Author: Ted Roche
Posted: 2017-07-27 12:10:05 Link
On Thu, Jul 27, 2017 at 11:20 AM,
<mbsoftwaresolutions@mbsoftwaresolutions.com> wrote:
> VFP9SP2
>
> Frustrated!!! All of the sudden my 2003 project code wants to rebel.
Well, it is fourteen. Teenagers!
--
Ted Roche
Ted Roche & Associates, LLC
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/CACW6n4uJyN9noQL0DmnYgPYWF+9FhPqgDwYyXNcOeJKwEA6vUw@mail.gmail.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
Author: Ted Roche
Posted: 2017-07-27 12:15:31 Link
What's SET('Development')?
Confirm your CurDir() is where you think you are.
Turn off VFP and try it again cold. Compiling often leaves things in memory.
On Thu, Jul 27, 2017 at 1:10 PM, Ted Roche <tedroche@gmail.com> wrote:
> On Thu, Jul 27, 2017 at 11:20 AM,
> <mbsoftwaresolutions@mbsoftwaresolutions.com> wrote:
>> VFP9SP2
>>
>> Frustrated!!! All of the sudden my 2003 project code wants to rebel.
>
> Well, it is fourteen. Teenagers!
>
>
> --
> Ted Roche
> Ted Roche & Associates, LLC
--
Ted Roche
Ted Roche & Associates, LLC
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/CACW6n4sOW=DodtPsTuJ71hCky_w-Lo-W0Y1is-4X8MgXQm7FGQ@mail.gmail.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
Author: mbsoftwaresolutions@mbsoftwaresolutions.com
Posted: 2017-07-27 13:49:00 Link
On 2017-07-27 11:38, Alan Bourke wrote:
> I get similar issues sometimes. It's always paths or old FXP files
> without debug info in them.
What's weird is I've deleted the FXPs and recompiled though. DebugInfo
is checked in the Project setup too.
>
> Are the PRG files built into the EXE via the project ?
Yes, these PRGs are included in the EXE.
>
> Do you have 'set classlib to progs\_bizobj.prg additive' somewhere at
> the setup of your application? I find it's best to be explicit rather
> than relying on search paths to find it.
I didn't use SET PROCEDURE before since I was explicit in the 2nd parm
of the NewObject(class,location) call saying where to get it.
>
> Have you tried building an APP instead of an EXE and running that in
> VFP?
Just tried...no different.
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/9dcd943a2a8b13ce83d0058d28e004a7@mbsoftwaresolutions.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.
Author: mbsoftwaresolutions@mbsoftwaresolutions.com
Posted: 2017-07-27 13:49:50 Link
On 2017-07-27 13:15, Ted Roche wrote:
> What's SET('Development')?
>
> Confirm your CurDir() is where you think you are.
>
> Turn off VFP and try it again cold. Compiling often leaves things in
> memory.
SET DEVELOPMENT is ON. CurDir() confirms it's in the app/project
folder. I've restarted VFP repeatedly. Even restarted the entire
machine!
Added SET PROCEDURE to .\progs\_bizobj.prg, .\progs\_dataobj.prg in Main
program right after startup and confirmation of current proper
folder...no change.
Did a SET STEP ON before the object created. I added a SET PROCEDURE TO
c:\dev\fabmate11\progs\_bizobj.prg ahead of it and changed the NewObject
to Createobject. Here's a screenshot of that:
https://www.screencast.com/t/YOTQF4D5Xsw STILL same bad behavior.
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/370f6091991345d70d198838a63d693f@mbsoftwaresolutions.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.
Author: Frank Cazabon
Posted: 2017-07-27 14:04:43 Link
At times like these I have added a SET STEP ON in the code module that
is showing up as "Source not found" rather than before it.
Frank.
Frank Cazabon
On 27/07/2017 02:49 PM, mbsoftwaresolutions@mbsoftwaresolutions.com wrote:
> On 2017-07-27 13:15, Ted Roche wrote:
>> What's SET('Development')?
>>
>> Confirm your CurDir() is where you think you are.
>>
>> Turn off VFP and try it again cold. Compiling often leaves things in
>> memory.
>
>
> SET DEVELOPMENT is ON. CurDir() confirms it's in the app/project
> folder. I've restarted VFP repeatedly. Even restarted the entire
> machine!
>
> Added SET PROCEDURE to .\progs\_bizobj.prg, .\progs\_dataobj.prg in
> Main program right after startup and confirmation of current proper
> folder...no change.
>
> Did a SET STEP ON before the object created. I added a SET PROCEDURE
> TO c:\dev\fabmate11\progs\_bizobj.prg ahead of it and changed the
> NewObject to Createobject. Here's a screenshot of that:
> https://www.screencast.com/t/YOTQF4D5Xsw STILL same bad behavior.
>
>
[excessive quoting removed by server]
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/968150ba-bc44-7554-d2dc-968dbd7c0710@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.
Author: mbsoftwaresolutions@mbsoftwaresolutions.com
Posted: 2017-07-27 14:06:35 Link
I found a workaround. I had a copy of the PJX/PJT from a year ago from
a source code backup. Works now. Bottom line -- I think something
wonky with the Project file. Wonder if that weird quirk could lead to
this wonky "ghosting" behavior they're seeing? It's not consistent
either. Oh well. Onward.
Ugh.
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/5b2a75870cdab3fb406fee47b172f061@mbsoftwaresolutions.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.