Re: TADOQuery, OnFilterRecord and Locate
- From: "Isaac Alexander" <isaacNOSPAM@xxxxxxxxxxxxxxxxxxx>
- Date: Tue, 15 Aug 2006 10:33:10 -0700
"Kevin Frevert" <kevin@xxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:44e1c549$1@xxxxxxxxxxxxxxxxxxxxxxxxx
"Isaac Alexander" <isaacNOSPAM@xxxxxxxxxxxxxxxxxxx> wrote in message
news:44e1007a$1@xxxxxxxxxxxxxxxxxxxxxxxxx
The BDE handled this quite nicely since it would only fire the
OnFilterRecord event for enough records to fill the grid which made for
great performance.
We ran into a similar issue (going from BDE->ADO), which we ended up
having to have multiple round-trips to the server. At the time it seemed
like a huge problem (which is was), but it forced us to re-think what the
application was really needing to do and ended up re-writing the process
to a single stored procedure call. Almost 5 years later, users still
enjoy nearly instantaneous response times.
How much work is being done in the stored procedure? My list is an conflict
checking sampling module that checks availability, licenses, skills, plus up
to 20 other search criteria. I'm worried that the stored procedure will take
a long time.
.
- Follow-Ups:
- Re: TADOQuery, OnFilterRecord and Locate
- From: Kevin Frevert
- Re: TADOQuery, OnFilterRecord and Locate
- References:
- TADOQuery, OnFilterRecord and Locate
- From: Isaac Alexander
- Re: TADOQuery, OnFilterRecord and Locate
- From: Kevin Frevert
- TADOQuery, OnFilterRecord and Locate
- Prev by Date: Re: TADOQuery, OnFilterRecord and Locate
- Next by Date: Re: TADOQuery, OnFilterRecord and Locate
- Previous by thread: Re: TADOQuery, OnFilterRecord and Locate
- Next by thread: Re: TADOQuery, OnFilterRecord and Locate
- Index(es):
Relevant Pages
|