Re: Move on, nothing to see here.

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Andrew Howell (ajh_at_work)
Date: 10/20/04 

Date: Wed, 20 Oct 2004 11:43:22 +0100

Andrew Howell wrote:
> Andrew Howell wrote:
> I think it's time to take a break.

Errrr, I've had a break. I put the code back into the large procedure file
and removed the separate .PRGs and rebuilt. Sure enough the application ran
quickly again.

I removed the procedures from the procedure file and rebuilt. Sure enough,
the separate files were added to the project again but now the application
is still running quickly.

Does anyone have a plausible explanation for what went on here or should I
pretend it never happened?
I'd already done a "rebuild all" when I first split the procedures out so I
know that's out of the question. 

--
WTF?
Andrew Howell

Relevant Pages

  • Re: procedure in separate files = slow execution?
    ... Andrew Howell wrote: ... > #INCLUDE the files in the procedure file. ... > exe, why should code location in the source have such a negative ...
    (microsoft.public.fox.programmer.exchange)
  • Re: procedure in separate files = slow execution?
    ... > Andrew Howell wrote: ... > file and removed the separate .PRGs and rebuilt. ... > I removed the procedures from the procedure file and rebuilt. ... does having a bunch of separate procedures in separate .PRGs run a LOT ...
    (microsoft.public.fox.programmer.exchange)
  • Re: procedure in separate files = slow execution?
    ... "Andrew Howell" wrote: ... you'd've copied the needed procs from the original procedure file into a new ... procedure file, except it would have a prg extension. ...
    (microsoft.public.fox.programmer.exchange)