Re: Slow VFP 8 Forms vs. 2.6 Screens
From: Fred Taylor (ftaylor_at_mvps.org!REMOVE)
Date: 03/23/04
- Next message: PRiveraSr: "Re: Column locking pleasant side-effect"
- Previous message: Gary: "about autogenerate a record!"
- In reply to: George Shubin: "Re: Slow VFP 8 Forms vs. 2.6 Screens"
- Next in thread: George Shubin: "Re: Slow VFP 8 Forms vs. 2.6 Screens"
- Reply: George Shubin: "Re: Slow VFP 8 Forms vs. 2.6 Screens"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 22 Mar 2004 17:59:33 -0700
Ah, I see, the Political Monster of Useless Decrees strikes again. All I
can say is "You'll be sorry!". :(
Fred
Microsoft Visual FoxPro MVP
"George Shubin" <dx@dxonline.com> wrote in message
news:eJASRGCEEHA.2424@TK2MSFTNGP09.phx.gbl...
> Thanks, Fred. I would love to be able to refactor the app and do it right
> for VFP, but unfortunately the unrealistic completion deadline is
> politically driven, so there is barely enough time to do a plain-jane
> functional conversion. Unless there is a magic bullet to our problem, I'm
> afraid we've been set up by management for failure.
>
> GS
>
>
>
> "Fred Taylor" <ftaylor@mvps.org!REMOVE> wrote in message
> news:OO7DvxuDEHA.2564@TK2MSFTNGP11.phx.gbl...
> >
> > "George Shubin" <dx@dxonline.com> wrote in message
> > news:eGT$ZEsDEHA.3236@TK2MSFTNGP09.phx.gbl...
> > > 1. Memvar initialization and data table preparation
> >
> > Usually not a good idea. Properties of the forms for values that the
form
> > requires locally is a better implementation. Tables can be opened ahead
> of
> > time, but even that can present a danger to corruption that data
buffering
> > would reduce.
> >
> > > 2. DO FORM xyz NAME xzy
> > > DO WHILE IsForm("xyz")
> > > DOEVENTS FORCE
> > > ENDDO
> >
> > DO FORM xyz NAME xyz
> > READ EVENTS
> >
> >
> > > 3. Logic to occur after form is closed
> >
> > Code in the QueryUnload of the form?
> >
> > > 4. RETURN
> > >
> > > 5. Form's When logic for each control
> > >
> > > 6. Form's Valid and Click logic for each control
> >
> > Valid can still be used, but if you need to push focus to some other
> > control, you'll have to use LostFocus of the control instead.
> >
> > > 7. Misc. required functions
> >
> > Misc. required function can still exist in a SET PROCEDURE file, or they
> can
> > be methods to an application object, or even just built into your own
base
> > level classes as needed.
> >
> > Your best bet is to NOT fight VFP at every turn by trying to stick with
> old
> > FPx way of doing things. The VFP object model is really quite extensive
> and
> > flexible, as long as you don't limit your thinking to just the FPx way
of
> > life.
> >
> > Fred
> > Microsoft Visual FoxPro MVP
> >
> >
>
>
- Next message: PRiveraSr: "Re: Column locking pleasant side-effect"
- Previous message: Gary: "about autogenerate a record!"
- In reply to: George Shubin: "Re: Slow VFP 8 Forms vs. 2.6 Screens"
- Next in thread: George Shubin: "Re: Slow VFP 8 Forms vs. 2.6 Screens"
- Reply: George Shubin: "Re: Slow VFP 8 Forms vs. 2.6 Screens"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
