Re: Problems saving effects entire app
From: Anders Altberg (x_pragma_at_telia.com)
Date: 09/23/04
- Next message: Matthew Freeze: "Allowing a user to save a project to a new directory"
- Previous message: Stefan Wuebbe: "Re: Problems saving effects entire app"
- In reply to: Anonymous: "Re: Problems saving effects entire app"
- Next in thread: Anonymous: "Re: Problems saving effects entire app"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 23 Sep 2004 11:03:54 +0200
Hi Anonymous
Updatable datatables cannot be rolled into an exe. There's no point,
speedwise, ever rolling any data tables into an exe. VFP databases have
nothing to do with this. They are actually separate metadata VFP tables and
not some sort or shell contaniner for tables, like client/server databases.
SCAN is enourmously fast. but SCAN FOR lExpr is only optimzed given
appropriate indexes on the same expression.
You're barking up the wrong tree I'm afraid.
-Anders
"Anonymous" <wipeout64@hotmail.com> wrote in message
news:c835bafc.0409221728.2b9fa424@posting.google.com...
> Thanks for your response.
>
> This app has been altered in the visual atmosphere for the past 6
> years. Pretty near all screens were re-done upon conversion. Most
> programs were saved. By now, most of the code has been changed enough
> to say it's finally a re-write. The tables this app uses are updated
> quarterly and are separate from the app as these tables are not
> created by me and are far too big for the app to hold within the exe,
> so databases haven't been used. I believe 9.0 isn't coming out until
> March. We need to address this saving and speed issue sooner. It seems
> that 8.0 is more stable in the indexing and table department. Am I
> correct?
>
>
>
>
>
>
>
> "Rick Bean" <rgbean@unrealmelange-inc.com> wrote in message
news:<#3GckRNoEHA.2900@TK2MSFTNGP09.phx.gbl>...
> > I'll assume you mean FPW 2.5/2.6 that ran on Windows 3.1x. How was this
> > application converted? Did your users upgrade the hardware with the
> > "new" version - especially memory? With each new version (9.0 will be
> > out soon!), less and less emphasis has been placed on running the old
> > xBase code "fast". Consider a rewrite - it's the only way to take
> > advantage of the newer versions.
> >
> > Rick
> >
> > "Anonymous" <wipeout64@hotmail.com> wrote in message
> > news:c835bafc.0409220930.7cdd6856@posting.google.com...
> > >I have an application that was created with FoxPro for windows 3.1,
> > > then was converted to FP Visual 6.0, then 7.0. Ever since the initial
> > > conversion to visual, saving data had been a problem, especially
> > > within scans. In order to save properly, I had to resort to a do-while
> > > loop or slow the scan down with 'wait' clauses. This slows the app's
> > > process down considerably and am getting complaints that FoxPro for
> > > windows is faster. What can be done to improve it's speed within
> > > scans/loops? I'm planning to upgrade the app to version 8.0. Will this
> > > solve the saving problem? or are there suggestions as to what type of
> > > programming to avoid when there is a saving problem?
- Next message: Matthew Freeze: "Allowing a user to save a project to a new directory"
- Previous message: Stefan Wuebbe: "Re: Problems saving effects entire app"
- In reply to: Anonymous: "Re: Problems saving effects entire app"
- Next in thread: Anonymous: "Re: Problems saving effects entire app"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
