OK - here at my day job - most times I am working on older style systems
- even the screen continue to look like FoxPro for DOS with White Text
on Blue Screens. Its pretty scary to be in the year 2012 - but, still
almost stuck in the DOS of DOS Circa 1989. And, as such, most of the
coding I do is purely PRG's with VERY Few Graphical Screen work.
However, on occasion - I get to be lucky enough to work on a separate
project that is purely VFP, with regular graphical screens, a normal VFP
menu - and getting to compile an EXE.
Now - normally, when working with PRG/FXP's - I almost never come across
this problem - as stated in the Subject. However, when compiling an EXE
and running it - I have at times run into this problem. I put a Set Step
On in a program or a screen/Form - and when its running (I start running
the EXE from within a session of VFP) - I get the error in the Debugger
of:
Source Not Available
I'm getting it now - and its frustrated me so - that I decided I would
post the problem here!
Any thought?
TIA,
-K-
Senior Developer
Waitex Information System, Inc.
P Save a tree. Don't print this e-mail unless it's really necessary.
--- StripMime Report -- processed MIME parts ---
multipart/alternative
text/plain (text body -- kept)
text/html
---
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/289EA162F5642645B5CF64D624C66A140B7CE927@us-ny-mail-002.waitex.net
** 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.
I'm assuming you're working in a debug environment as opposed to production.
Is the path to where your source code is located in the search path of your EXE? If not, can you use a CONFIG.FPW file to set your path at runtime?
Is your project set to include DEBUG info? (See the project options.)
--
rk
-----Original Message-----
From: profoxtech-bounces@leafe.com [mailto:profoxtech-bounces@leafe.com] On Behalf Of Kurt Wendt
Sent: Thursday, February 02, 2012 4:52 PM
To: profoxtech@leafe.com
Subject: Debugger - Source Not Available
OK - here at my day job - most times I am working on older style systems
- even the screen continue to look like FoxPro for DOS with White Text on Blue Screens. Its pretty scary to be in the year 2012 - but, still almost stuck in the DOS of DOS Circa 1989. And, as such, most of the coding I do is purely PRG's with VERY Few Graphical Screen work.
However, on occasion - I get to be lucky enough to work on a separate project that is purely VFP, with regular graphical screens, a normal VFP menu - and getting to compile an EXE.
Now - normally, when working with PRG/FXP's - I almost never come across this problem - as stated in the Subject. However, when compiling an EXE and running it - I have at times run into this problem. I put a Set Step On in a program or a screen/Form - and when its running (I start running the EXE from within a session of VFP) - I get the error in the Debugger
of:
Source Not Available
I'm getting it now - and its frustrated me so - that I decided I would post the problem here!
Any thought?
TIA,
-K-
Senior Developer
Waitex Information System, Inc.
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/DF1EEF11E586A64FB54A97F22A8BD0441D4A7D627D@ACKBWDDQH1.artfact.local
** 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.
If I remember correctly, if you make a change to one of the programs
and don't rebuild the project that will occurr or some combination of
the above....
Regards,
Desmond.
On 2 February 2012 15:57, Richard Kaye <RKaye@artfact.com> wrote:
> I'm assuming you're working in a debug environment as opposed to production.
>
> Is the path to where your source code is located in the search path of your EXE? If not, can you use a CONFIG.FPW file to set your path at runtime?
>
> Is your project set to include DEBUG info? (See the project options.)
>
> --
> rk
>
>
> -----Original Message-----
> From: profoxtech-bounces@leafe.com [mailto:profoxtech-bounces@leafe.com] On Behalf Of Kurt Wendt
> Sent: Thursday, February 02, 2012 4:52 PM
> To: profoxtech@leafe.com
> Subject: Debugger - Source Not Available
>
> OK - here at my day job - most times I am working on older style systems
> - even the screen continue to look like FoxPro for DOS with White Text on Blue Screens. Its pretty scary to be in the year 2012 - but, still almost stuck in the DOS of DOS Circa 1989. And, as such, most of the coding I do is purely PRG's with VERY Few Graphical Screen work.
>
>
>
> However, on occasion - I get to be lucky enough to work on a separate project that is purely VFP, with regular graphical screens, a normal VFP menu - and getting to compile an EXE.
>
>
>
> Now - normally, when working with PRG/FXP's - I almost never come across this problem - as stated in the Subject. However, when compiling an EXE and running it - I have at times run into this problem. I put a Set Step On in a program or a screen/Form - and when its running (I start running the EXE from within a session of VFP) - I get the error in the Debugger
> of:
>
> Source Not Available
>
>
>
> I'm getting it now - and its frustrated me so - that I decided I would post the problem here!
>
>
>
> Any thought?
>
> TIA,
>
> -K-
>
>
>
> Senior Developer
>
> Waitex Information System, Inc.
>
[excessive quoting removed by server]
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/CAAJXvaNbTY=NU+uubOsONjhqNJudKtfnq0CcUZN0AENMNO7joQ@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.
Actually - I not only did a rebuild of the project, and of the EXE - I also attempted to build it as an APP - and run that. But, still the same problem.
I am, however, going to right now check into some of the suggestions from Richard - and see if I can make it work right...
Thanks again,
-K-
-----Original Message-----
From: profoxtech-bounces@leafe.com [mailto:profoxtech-bounces@leafe.com] On Behalf Of Desmond Lloyd
Sent: Thursday, February 02, 2012 5:05 PM
If I remember correctly, if you make a change to one of the programs
and don't rebuild the project that will occurr or some combination of
the above....
Regards,
Desmond.
On 2 February 2012 15:57, Richard Kaye <RKaye@artfact.com> wrote:
> I'm assuming you're working in a debug environment as opposed to production.
>
> Is the path to where your source code is located in the search path of your EXE? If not, can you use a CONFIG.FPW file to set your path at runtime?
>
> Is your project set to include DEBUG info? (See the project options.)
>
> --
> rk
>
> -----Original Message-----
> From: profoxtech-bounces@leafe.com [mailto:profoxtech-bounces@leafe.com] On Behalf Of Kurt Wendt
> Sent: Thursday, February 02, 2012 4:52 PM
> To: profoxtech@leafe.com
> Subject: Debugger - Source Not Available
>
> OK - here at my day job - most times I am working on older style systems
> - even the screen continue to look like FoxPro for DOS with White Text on Blue Screens. Its pretty scary to be in the year 2012 - but, still almost stuck in the DOS of DOS Circa 1989. And, as such, most of the coding I do is purely PRG's with VERY Few Graphical Screen work.
>
> However, on occasion - I get to be lucky enough to work on a separate project that is purely VFP, with regular graphical screens, a normal VFP menu - and getting to compile an EXE.
>
> Now - normally, when working with PRG/FXP's - I almost never come across this problem - as stated in the Subject. However, when compiling an EXE and running it - I have at times run into this problem. I put a Set Step On in a program or a screen/Form - and when its running (I start running the EXE from within a session of VFP) - I get the error in the Debugger
> of:
> Source Not Available
>
>
>
> I'm getting it now - and its frustrated me so - that I decided I would post the problem here!
>
>
> Any thought?
>
> TIA,
> -K-
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/289EA162F5642645B5CF64D624C66A140B7CE929@us-ny-mail-002.waitex.net
** 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.
As for the Env. - I'm building the App in our office, and when its done
- it will be sent to the client. It's a new App for the client, but
based upon an older one used for other clients (its for UCC Label
printing).
I did just now set the project to include DEBUG info - with the project
options - but that didn't help.
Am going to look into the other suggestions you made - like the search
path & Config file.
-K-
-----Original Message-----
From: profoxtech-bounces@leafe.com [mailto:profoxtech-bounces@leafe.com]
On Behalf Of Richard Kaye
Sent: Thursday, February 02, 2012 4:57 PM
To: profoxtech@leafe.com
Subject: RE: Debugger - Source Not Available
I'm assuming you're working in a debug environment as opposed to
production.
Is the path to where your source code is located in the search path of
your EXE? If not, can you use a CONFIG.FPW file to set your path at
runtime?
Is your project set to include DEBUG info? (See the project options.)
--
rk
-----Original Message-----
From: profoxtech-bounces@leafe.com [mailto:profoxtech-bounces@leafe.com]
On Behalf Of Kurt Wendt
Sent: Thursday, February 02, 2012 4:52 PM
To: profoxtech@leafe.com
Subject: Debugger - Source Not Available
OK - here at my day job - most times I am working on older style systems
- even the screen continue to look like FoxPro for DOS with White Text
on Blue Screens. Its pretty scary to be in the year 2012 - but, still
almost stuck in the DOS of DOS Circa 1989. And, as such, most of the
coding I do is purely PRG's with VERY Few Graphical Screen work.
However, on occasion - I get to be lucky enough to work on a separate
project that is purely VFP, with regular graphical screens, a normal VFP
menu - and getting to compile an EXE.
Now - normally, when working with PRG/FXP's - I almost never come across
this problem - as stated in the Subject. However, when compiling an EXE
and running it - I have at times run into this problem. I put a Set Step
On in a program or a screen/Form - and when its running (I start running
the EXE from within a session of VFP) - I get the error in the Debugger
of:
Source Not Available
I'm getting it now - and its frustrated me so - that I decided I would
post the problem here!
Any thought?
TIA,
-K-
Senior Developer
Waitex Information System, Inc.
[excessive quoting removed by server]
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/289EA162F5642645B5CF64D624C66A140B7CE92A@us-ny-mail-002.waitex.net
** 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.
Save your compiled exe to the same folder where the .pjx is located.
Change to the folder you want to run the program and then run the exe from
the folder where the .pjx is located
Jerry
-----Original Message-----
From: profox-bounces@leafe.com [mailto:profox-bounces@leafe.com] On Behalf
Of Kurt Wendt
Sent: Thursday, February 02, 2012 4:15 PM
To: profox@leafe.com
Subject: RE: Debugger - Source Not Available
Actually - I not only did a rebuild of the project, and of the EXE - I also
attempted to build it as an APP - and run that. But, still the same problem.
I am, however, going to right now check into some of the suggestions from
Richard - and see if I can make it work right...
Thanks again,
-K-
-----Original Message-----
From: profoxtech-bounces@leafe.com [mailto:profoxtech-bounces@leafe.com] On
Behalf Of Desmond Lloyd
Sent: Thursday, February 02, 2012 5:05 PM
If I remember correctly, if you make a change to one of the programs
and don't rebuild the project that will occurr or some combination of
the above....
Regards,
Desmond.
On 2 February 2012 15:57, Richard Kaye <RKaye@artfact.com> wrote:
> I'm assuming you're working in a debug environment as opposed to
production.
>
> Is the path to where your source code is located in the search path of
your EXE? If not, can you use a CONFIG.FPW file to set your path at runtime?
>
> Is your project set to include DEBUG info? (See the project options.)
>
> --
> rk
>
> -----Original Message-----
> From: profoxtech-bounces@leafe.com [mailto:profoxtech-bounces@leafe.com]
On Behalf Of Kurt Wendt
> Sent: Thursday, February 02, 2012 4:52 PM
> To: profoxtech@leafe.com
> Subject: Debugger - Source Not Available
>
> OK - here at my day job - most times I am working on older style systems
> - even the screen continue to look like FoxPro for DOS with White Text on
Blue Screens. Its pretty scary to be in the year 2012 - but, still almost
stuck in the DOS of DOS Circa 1989. And, as such, most of the coding I do is
purely PRG's with VERY Few Graphical Screen work.
>
> However, on occasion - I get to be lucky enough to work on a separate
project that is purely VFP, with regular graphical screens, a normal VFP
menu - and getting to compile an EXE.
>
> Now - normally, when working with PRG/FXP's - I almost never come across
this problem - as stated in the Subject. However, when compiling an EXE and
running it - I have at times run into this problem. I put a Set Step On in a
program or a screen/Form - and when its running (I start running the EXE
from within a session of VFP) - I get the error in the Debugger
> of:
> Source Not Available
>
>
>
> I'm getting it now - and its frustrated me so - that I decided I would
post the problem here!
>
>
> Any thought?
>
> TIA,
> -K-
[excessive quoting removed by server]
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/4F0CE87B7BC0469AA33B8BE867896A3A@jerryfootePC
** 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.
You need to delete the compiled prg files. And to do that you need to close
VFP. what a bugger (de bugger)
Al
-----Original Message-----
From: Kurt Wendt
Sent: Thursday, February 02, 2012 11:14 PM
To: profoxtech@leafe.com
Subject: RE: Debugger - Source Not Available
Actually - I not only did a rebuild of the project, and of the EXE - I also
attempted to build it as an APP - and run that. But, still the same problem.
I am, however, going to right now check into some of the suggestions from
Richard - and see if I can make it work right...
Thanks again,
-K-
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/21603A4A899843E6AD81E1ABECC59566@gslredacer
** 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.
Hey Jerry - that worked like a BREEZE! I should have been working that way from the Start.
We normally have this Printer application installed in a C: drive location, so that's the way I was working with it and testing it.
But, I now ran it from the Network location where I was working on it - and now I can see the Code just FINE in the Debugger!
As usual - this List ROCKS - Thank you Jerry - as well as YOU ED - For Creating & Hosting this list!!!
Now I can end my day on an upswing!
-K-
-----Original Message-----
From: profoxtech-bounces@leafe.com [mailto:profoxtech-bounces@leafe.com] On Behalf Of Jerry Foote
Sent: Thursday, February 02, 2012 5:42 PM
To: profoxtech@leafe.com
Subject: RE: Debugger - Source Not Available
Save your compiled exe to the same folder where the .pjx is located.
Change to the folder you want to run the program and then run the exe from
the folder where the .pjx is located
Jerry
-----Original Message-----
From: profox-bounces@leafe.com [mailto:profox-bounces@leafe.com] On Behalf
Of Kurt Wendt
Sent: Thursday, February 02, 2012 4:15 PM
To: profox@leafe.com
Subject: RE: Debugger - Source Not Available
Actually - I not only did a rebuild of the project, and of the EXE - I also
attempted to build it as an APP - and run that. But, still the same problem.
I am, however, going to right now check into some of the suggestions from
Richard - and see if I can make it work right...
Thanks again,
-K-
-----Original Message-----
From: profoxtech-bounces@leafe.com [mailto:profoxtech-bounces@leafe.com] On
Behalf Of Desmond Lloyd
Sent: Thursday, February 02, 2012 5:05 PM
If I remember correctly, if you make a change to one of the programs
and don't rebuild the project that will occurr or some combination of
the above....
Regards,
Desmond.
On 2 February 2012 15:57, Richard Kaye <RKaye@artfact.com> wrote:
> I'm assuming you're working in a debug environment as opposed to
production.
>
> Is the path to where your source code is located in the search path of
your EXE? If not, can you use a CONFIG.FPW file to set your path at runtime?
>
> Is your project set to include DEBUG info? (See the project options.)
>
> --
> rk
>
> -----Original Message-----
> From: profoxtech-bounces@leafe.com [mailto:profoxtech-bounces@leafe.com]
On Behalf Of Kurt Wendt
> Sent: Thursday, February 02, 2012 4:52 PM
> To: profoxtech@leafe.com
> Subject: Debugger - Source Not Available
>
> OK - here at my day job - most times I am working on older style systems
> - even the screen continue to look like FoxPro for DOS with White Text on
Blue Screens. Its pretty scary to be in the year 2012 - but, still almost
stuck in the DOS of DOS Circa 1989. And, as such, most of the coding I do is
purely PRG's with VERY Few Graphical Screen work.
>
> However, on occasion - I get to be lucky enough to work on a separate
project that is purely VFP, with regular graphical screens, a normal VFP
menu - and getting to compile an EXE.
>
> Now - normally, when working with PRG/FXP's - I almost never come across
this problem - as stated in the Subject. However, when compiling an EXE and
running it - I have at times run into this problem. I put a Set Step On in a
program or a screen/Form - and when its running (I start running the EXE
from within a session of VFP) - I get the error in the Debugger
> of:
> Source Not Available
>
>
>
> I'm getting it now - and its frustrated me so - that I decided I would
post the problem here!
>
>
> Any thought?
>
> TIA,
> -K-
[excessive quoting removed by server]
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/289EA162F5642645B5CF64D624C66A140B7CE92C@us-ny-mail-002.waitex.net
** 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.
I have had these issue and for me the solution was to
USE MYPROG.PJX
Now locate prgs or scx's not in the default location
The other times when I've had this problem is with reports where I
referenced a PRG and the PRG was not in the project (standalone
reports/frx's)
S
On Fri, Feb 3, 2012 at 11:14 AM, Kurt Wendt <kurtwendt@waitex.com> wrote:
> Actually - I not only did a rebuild of the project, and of the EXE - I
> also attempted to build it as an APP - and run that. But, still the same
> problem.
>
> I am, however, going to right now check into some of the suggestions from
> Richard - and see if I can make it work right...
>
> Thanks again,
> -K-
>
>
> -----Original Message-----
> From: profoxtech-bounces@leafe.com [mailto:profoxtech-bounces@leafe.com]
> On Behalf Of Desmond Lloyd
> Sent: Thursday, February 02, 2012 5:05 PM
>
> If I remember correctly, if you make a change to one of the programs
> and don't rebuild the project that will occurr or some combination of
> the above....
>
> Regards,
> Desmond.
>
> On 2 February 2012 15:57, Richard Kaye <RKaye@artfact.com> wrote:
> > I'm assuming you're working in a debug environment as opposed to
> production.
> >
> > Is the path to where your source code is located in the search path of
> your EXE? If not, can you use a CONFIG.FPW file to set your path at runtime?
> >
> > Is your project set to include DEBUG info? (See the project options.)
> >
> > --
> > rk
> >
> > -----Original Message-----
> > From: profoxtech-bounces@leafe.com [mailto:profoxtech-bounces@leafe.com]
> On Behalf Of Kurt Wendt
> > Sent: Thursday, February 02, 2012 4:52 PM
> > To: profoxtech@leafe.com
> > Subject: Debugger - Source Not Available
> >
> > OK - here at my day job - most times I am working on older style systems
> > - even the screen continue to look like FoxPro for DOS with White Text
> on Blue Screens. Its pretty scary to be in the year 2012 - but, still
> almost stuck in the DOS of DOS Circa 1989. And, as such, most of the coding
> I do is purely PRG's with VERY Few Graphical Screen work.
> >
> > However, on occasion - I get to be lucky enough to work on a separate
> project that is purely VFP, with regular graphical screens, a normal VFP
> menu - and getting to compile an EXE.
> >
> > Now - normally, when working with PRG/FXP's - I almost never come across
> this problem - as stated in the Subject. However, when compiling an EXE and
> running it - I have at times run into this problem. I put a Set Step On in
> a program or a screen/Form - and when its running (I start running the EXE
> from within a session of VFP) - I get the error in the Debugger
> > of:
> > Source Not Available
> >
> >
> >
> > I'm getting it now - and its frustrated me so - that I decided I would
> post the problem here!
> >
> >
> > Any thought?
> >
> > TIA,
> > -K-
>
[excessive quoting removed by server]
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/CAG1nNy8Qrby2OhgS3wipdg8QJNMCELSn65nZt-1cEbRFQnLxuw@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.
Sytze
I create a prg in project and in the code I place this following code
If .F.
Report form xxx preview
Report form yyy preview
Report form zzz preview
endif
Every time I add a report I add the report to this prg. Since the code will
never execute you have no problems but the compiler always includes the
reports in the exe.
-----Original Message-----
From: profox-bounces@leafe.com [mailto:profox-bounces@leafe.com] On Behalf
Of Sytze de Boer
Sent: Thursday, February 02, 2012 4:59 PM
To: profox@leafe.com
Subject: Re: Debugger - Source Not Available
I have had these issue and for me the solution was to
USE MYPROG.PJX
Now locate prgs or scx's not in the default location
The other times when I've had this problem is with reports where I
referenced a PRG and the PRG was not in the project (standalone
reports/frx's)
S
On Fri, Feb 3, 2012 at 11:14 AM, Kurt Wendt <kurtwendt@waitex.com> wrote:
> Actually - I not only did a rebuild of the project, and of the EXE - I
> also attempted to build it as an APP - and run that. But, still the same
> problem.
>
> I am, however, going to right now check into some of the suggestions from
> Richard - and see if I can make it work right...
>
> Thanks again,
> -K-
>
>
> -----Original Message-----
> From: profoxtech-bounces@leafe.com [mailto:profoxtech-bounces@leafe.com]
> On Behalf Of Desmond Lloyd
> Sent: Thursday, February 02, 2012 5:05 PM
>
> If I remember correctly, if you make a change to one of the programs
> and don't rebuild the project that will occurr or some combination of
> the above....
>
> Regards,
> Desmond.
>
> On 2 February 2012 15:57, Richard Kaye <RKaye@artfact.com> wrote:
> > I'm assuming you're working in a debug environment as opposed to
> production.
> >
> > Is the path to where your source code is located in the search path of
> your EXE? If not, can you use a CONFIG.FPW file to set your path at
runtime?
> >
> > Is your project set to include DEBUG info? (See the project options.)
> >
> > --
> > rk
> >
> > -----Original Message-----
> > From: profoxtech-bounces@leafe.com [mailto:profoxtech-bounces@leafe.com]
> On Behalf Of Kurt Wendt
> > Sent: Thursday, February 02, 2012 4:52 PM
> > To: profoxtech@leafe.com
> > Subject: Debugger - Source Not Available
> >
> > OK - here at my day job - most times I am working on older style systems
> > - even the screen continue to look like FoxPro for DOS with White Text
> on Blue Screens. Its pretty scary to be in the year 2012 - but, still
> almost stuck in the DOS of DOS Circa 1989. And, as such, most of the
coding
> I do is purely PRG's with VERY Few Graphical Screen work.
> >
> > However, on occasion - I get to be lucky enough to work on a separate
> project that is purely VFP, with regular graphical screens, a normal VFP
> menu - and getting to compile an EXE.
> >
> > Now - normally, when working with PRG/FXP's - I almost never come across
> this problem - as stated in the Subject. However, when compiling an EXE
and
> running it - I have at times run into this problem. I put a Set Step On in
> a program or a screen/Form - and when its running (I start running the EXE
> from within a session of VFP) - I get the error in the Debugger
> > of:
> > Source Not Available
> >
> >
> >
> > I'm getting it now - and its frustrated me so - that I decided I would
> post the problem here!
> >
> >
> > Any thought?
> >
> > TIA,
> > -K-
>
[excessive quoting removed by server]
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/C229BB0023CD460AB8F64C6EC9DB1881@jerryfootePC
** 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.