Glynn Owen wrote:

> I have a client who swears that his reports ran 5 times faster using
> BDE rather than DBISAM. Has anyone else had such problems when using
> remote connections?
>
> TIA,
> Glynn

I just finished isolating this report and running it all on its own. It
ran like blazes, so I think the problem is related to the 15 meg EXE in
which it is currently residing. At any rate, I can't believe it has
anything to do with DBISAM. My first guess is that "DisableControls"
has not been called on the primary dataset.

Thanks for the help,
Glynn

--

Glynn,

<< I just finished isolating this report and running it all on its own. It
ran like blazes, so I think the problem is related to the 15 meg EXE in
which it is currently residing. At any rate, I can't believe it has anything
to do with DBISAM. My first guess is that "DisableControls" has not been
called on the primary dataset. >>

That's usually a primary culprit.  Updating the controls constantly while
navigating will kill the performance stone dead.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim Young [Elevate Software] wrote:

> Glynn,
>
> << I just finished isolating this report and running it all on its
> own. It ran like blazes, so I think the problem is related to the 15
> meg EXE in which it is currently residing. At any rate, I can't
> believe it has anything to do with DBISAM. My first guess is that
> "DisableControls" has not been called on the primary dataset. >>
>
> That's usually a primary culprit.  Updating the controls constantly
> while navigating will kill the performance stone dead.

Yep - this simple change made the report run about 5 times faster!
Glynn

--