Subject | Re: [IBO] IBO and background threads |
---|---|
Author | andymurf2000@yahoo.co.uk |
Post date | 2001-03-20T16:40:04Z |
No its a read only database that holds 2.5million records. I didnt
know when originally designing the program that IB doesnt handle
record counts very quickly. I maybe should have used Paradox flat
index tables. However its too late to chage now and IB does a great
job with IBO when the system is used across a large network.
I just want to be able to do a server side record count in the
background so that the user doesn't wait. I dont mind using a second
connection or query. I can copy the 'where' part of the query from
the main query but substitute my 'select field1, field2 etc'
with 'select count(*)'
Any ideas on what components to drop on my form and any code to make
this happen?
Like I say Im new to threads so I aint got a clue! :-)
Cheers,
Andy.
know when originally designing the program that IB doesnt handle
record counts very quickly. I maybe should have used Paradox flat
index tables. However its too late to chage now and IB does a great
job with IBO when the system is used across a large network.
I just want to be able to do a server side record count in the
background so that the user doesn't wait. I dont mind using a second
connection or query. I can copy the 'where' part of the query from
the main query but substitute my 'select field1, field2 etc'
with 'select count(*)'
Any ideas on what components to drop on my form and any code to make
this happen?
Like I say Im new to threads so I aint got a clue! :-)
Cheers,
Andy.
--- In IBObjects@y..., "Jason Wharton" <jwharton@i...> wrote:
> > I would use a separate TIB_Cursor for this and set the Callback
Properties
> > so, that the user can continue his work. So you wont have to deal
with
> treads.
>
> Normally this would work but I think if he does a record count it
will
> execute on the server and cause the client to block while it is
processing.
> A thread is the only way to get a large record count from the
server without
> making the client wait.
>
> I must say that I really think you should consider an alternative
way of
> doing this. Have you considered looking into maintaining stat
tables so that
> the counts are maintained for you?
>
> Then, is all you need is a quick query to look up the values.
>
> HTH,
> Jason Wharton
> CPS - Mesa AZ
> http://www.ibobjects.com