Re: TADOQuery, OnFilterRecord and Locate
- From: "Kevin Frevert" <kevin@xxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 15 Aug 2006 13:45:54 -0500
"Isaac Alexander" <isaacNOSPAM@xxxxxxxxxxxxxxxxxxx> wrote in message
news:44e2038e$1@xxxxxxxxxxxxxxxxxxxxxxxxx
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.
After we re-thought the process, not a lot. I don't know what your exact
needs are, but can the process be broken up in smaller processes? Maybe a
combination of database and non-database resources (ex. utilizing a O-O
design pattern like the Decorator pattern)? Maybe one of those situations
you don't know until you try?
There maybe a workaround or other useful information, take a look at:
http://www.fulltextsearch.com/
You can search on Borland specific newsgroups and see if anyone else is
having similar issues.
Good luck,
krf
.
- Follow-Ups:
- Re: TADOQuery, OnFilterRecord and Locate
- From: Isaac Alexander
- Re: TADOQuery, OnFilterRecord and Locate
- References:
- TADOQuery, OnFilterRecord and Locate
- From: Isaac Alexander
- Re: TADOQuery, OnFilterRecord and Locate
- From: Kevin Frevert
- Re: TADOQuery, OnFilterRecord and Locate
- From: Isaac Alexander
- TADOQuery, OnFilterRecord and Locate
- Prev by Date: Re: TADOQuery, OnFilterRecord and Locate
- Next by Date: Re: BDS 2006 ADO EOleException
- Previous by thread: Re: TADOQuery, OnFilterRecord and Locate
- Next by thread: Re: TADOQuery, OnFilterRecord and Locate
- Index(es):
Relevant Pages
|