Re: Pet peeve with debugging a PRG

Jeff Roberts wrote: > probably an odd practice that only I do, but I edit all my 2.6 dos/2.6 > unix code with vfp 9 and I keep a 2.6 window open for compiling. I > just have to make sure the file is closed in vfp when I compile it. I > get a lot of the benefits of the vfp editor this way, althoug

Re: Pet peeve with debugging a PRG

probably an odd practice that only I do, but I edit all my 2.6 dos/2.6 unix code with vfp 9 and I keep a 2.6 window open for compiling. I just have to make sure the file is closed in vfp when I compile it. I get a lot of the benefits of the vfp editor this way, although you do have to keep in min

Re: Pet peeve with debugging a PRG

Dear Peter: Thank you for the clarification. At 12:48 PM 8/3/2007, you wrote: >AFAIK this is not available in FPW2.6 You need to click edit/goto line >and put the number in. > >Peter -- Charles -- Mailto:[EMAIL PROTECTED] Website: http://homepages.uc.edu/

Re: Pet peeve with debugging a PRG

Charles Hart Enzer, M.D. wrote: > I can't get this keyboard command to work with FPW26a. > > How can I turn it on: > > Thank you. > > At 12:48 PM 8/3/2007, you wrote: > > >> My wife watched me count out lines one time and she said, "just right click >> and select 'go to'." I've been doing it ev

Re: Pet peeve with debugging a PRG

Ctrl+G = Next Find At 10:13 AM 9/9/2007, Paul Hill wrote: >On 9/9/07, Charles Hart Enzer, M.D. <[EMAIL PROTECTED]> wrote: > > I can't get this keyboard command to work with FPW26a. > >Tried Ctrl+G? > > > Thank you. > > > > At 12:48 PM 8/3/2007, you wrote: > > > > >My wife watched me count out line

Re: Pet peeve with debugging a PRG

On 9/9/07, Charles Hart Enzer, M.D. <[EMAIL PROTECTED]> wrote: > I can't get this keyboard command to work with FPW26a. Tried Ctrl+G? > Thank you. > > At 12:48 PM 8/3/2007, you wrote: > > >My wife watched me count out lines one time and she said, "just right click > >and select 'go to'." I've be

RE: Pet peeve with debugging a PRG

I can't get this keyboard command to work with FPW26a. How can I turn it on: Thank you. At 12:48 PM 8/3/2007, you wrote: >My wife watched me count out lines one time and she said, "just right click >and select 'go to'." I've been doing it ever since. > >Jeff > >Jeff Johnson >[EMAIL PROTECTED]

RE: Pet peeve with debugging a PRG

iday, August 03, 2007 9:23 AM To: profox@leafe.com Subject: Re: Pet peeve with debugging a PRG From: "Jack Skelley" <[EMAIL PROTECTED]> At one time there was an intelligent editor that did this automatically back in the days of FoxBase as a third party editor. But I can't remem

RE: Pet peeve with debugging a PRG

9:23 AM To: profox@leafe.com Subject: Re: Pet peeve with debugging a PRG From: "Jack Skelley" <[EMAIL PROTECTED]> At one time there was an intelligent editor that did this automatically back in the days of FoxBase as a third party editor. But I can't remember the editor

RE: Pet peeve with debugging a PRG

> -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > On Behalf Of Ted Roche > Sent: Friday, August 03, 2007 12:48 PM > To: [EMAIL PROTECTED] > Subject: Re: Pet peeve with debugging a PRG > > On 8/3/07, Allen <[EMAIL PROTECTED]> wrote: &g

Re: Pet peeve with debugging a PRG

On 8/3/07, Allen <[EMAIL PROTECTED]> wrote: > Yes, but I thought there was a keyboard shortcut. But Ive looked in VFP5 and > its not there either. Maybe fpw > Allen Alt-E for Edit, L for gotoLine is what I recall... I think there was a keyboard shortcut at one time, and it conflicted with somethi

RE: Pet peeve with debugging a PRG

with debugging a PRG Wasn't ctrl-G - Find Again? No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.476 / Virus Database: 269.11.2/933 - Release Date: 02/08/2007 14:22 ___ Post Messages to: ProFox@leaf

RE: Pet peeve with debugging a PRG

Wasn't ctrl-G - Find Again? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Allen Sent: 2007-08-03 1:53 PM To: [EMAIL PROTECTED] Subject: RE: Pet peeve with debugging a PRG I thought goto was control G at one time but not now it seems not

Re: Pet peeve with debugging a PRG

Control G is find aGain. Allen wrote: > I thought goto was control G at one time but not now it seems not > Allen > -- Richard Kaye Vice President Artfact/RFC Systems Voice: 617.219.1038 Fax: 617.219.1001 For the fastest response time, please send your support queries to: Technical Suppor

RE: Pet peeve with debugging a PRG

> -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > On Behalf Of Allen > Sent: Friday, August 03, 2007 10:53 AM > To: [EMAIL PROTECTED] > Subject: RE: Pet peeve with debugging a PRG > > I thought goto was control G at one time but not now it

RE: Pet peeve with debugging a PRG

I thought goto was control G at one time but not now it seems not Allen -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of mrgmhale Sent: 03 August 2007 19:05 To: [EMAIL PROTECTED] Subject: RE: Pet peeve with debugging a PRG > My wife watched me count

RE: Pet peeve with debugging a PRG

ter. Gil > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Jeff Johnson > Sent: Friday, August 03, 2007 12:48 PM > To: [EMAIL PROTECTED] > Subject: RE: Pet peeve with debugging a PRG > > > > -Original Message- > > From: [E

RE: Pet peeve with debugging a PRG

> -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > On Behalf Of MB Software Solutions > Sent: Friday, August 03, 2007 7:30 AM > To: [EMAIL PROTECTED] > Subject: Re: Pet peeve with debugging a PRG > > Jack Skelley wrote: > > That

Re: Pet peeve with debugging a PRG

lto:[EMAIL PROTECTED] On Behalf Of Dave Crozier > Sent: 2007-08-03 11:02 AM > To: [EMAIL PROTECTED] > Subject: RE: Pet peeve with debugging a PRG > > > Jack, > With VFP9 its in there already, just type: > > ifend <> > docase <> > dowhile <> > >

Re: Pet peeve with debugging a PRG

t; > Dave Crozier > > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf > Of Vince Teachout > Sent: 03 August 2007 14:34 > To: ProFox Email List > Subject: Re: Pet peeve with debugging a PRG > > Jack Skelley wrote: > >>

RE: Pet peeve with debugging a PRG

Cool! Thanks, Dave! Henry -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dave Crozier Sent: 2007-08-03 11:02 AM To: [EMAIL PROTECTED] Subject: RE: Pet peeve with debugging a PRG Jack, With VFP9 its in there already, just type: ifend <>

RE: Pet peeve with debugging a PRG

34 To: ProFox Email List Subject: Re: Pet peeve with debugging a PRG Jack Skelley wrote: > Michael: > When I write any code that has a END* construct as soon as I type in the IF (for example) on the next line I immediately > write the ENDIF statement. Then I go back and will in the stuf

Re: Pet peeve with debugging a PRG

Jack Skelley wrote: > That is if you struggle to get line numbering turned on. I tell it in the > properties to make line number on by default then when I come back it is > still off and need to turn it on again... > So I'm not the only one this happens tothanks for the tips, Jack! --

Re: Pet peeve with debugging a PRG

Jack Skelley wrote: > Michael: > When I write any code that has a END* construct as soon as I type in the IF > (for example) on the next line I immediately > write the ENDIF statement. Then I go back and will in the stuff between the 2 > lines with proper indents. > At one time there was an inte

Re: Pet peeve with debugging a PRG

From: "Jack Skelley" <[EMAIL PROTECTED]> At one time there was an intelligent editor that did this automatically back in the days of FoxBase as a third party editor. But I can't remember the editor's name... Jack Were you thinking of CEE ? Paul _

Re: Pet peeve with debugging a PRG

Michael: When I write any code that has a END* construct as soon as I type in the IF (for example) on the next line I immediately write the ENDIF statement. Then I go back and will in the stuff between the 2 lines with proper indents. At one time there was an intelligent editor that did this aut

Re: Pet peeve with debugging a PRG

MB Software Solutions wrote: > Getting "An IF | ELSE | ENDIF statement is missing." ...but of course > it's not showing me where. This PRG is the main data access prg that's > got bazillion lines in it. GR! > > If you compile the program there should then be a corresponding .ERR f

Re: Pet peeve with debugging a PRG

PrettyPrint??? MB Software Solutions wrote: > Getting "An IF | ELSE | ENDIF statement is missing." ...but of course > it's not showing me where. This PRG is the main data access prg that's > got bazillion lines in it. GR! > > My temporary sanity saver is just to comment out the proce

Pet peeve with debugging a PRG

Getting "An IF | ELSE | ENDIF statement is missing." ...but of course it's not showing me where. This PRG is the main data access prg that's got bazillion lines in it. GR! My temporary sanity saver is just to comment out the procedures 2/3 at a time where I've been working to fix th