All these mails about RecordCount made me take a look at TIBOQuery and
TIB_Query, and I discovered something I really liked: In the TIB_Query
you've made RecordCount a function rather than a property - and it much
easier to comprehend that a function requires time to complete than a
property (after all, many properties just read/writes values to/from fields).

So no question or work for you this time Jason, just a well done.

Set

At 01:26 01.12.2000 -0700, you wrote:

>NumberOfRecords is excellent to use in conjunction with search mode. I'm not
>in the slightest considering removing it...
>
>But, you raise an excellent point that there needs to be something to grab
>the developer's attention about it to take the issue into consideration.
>
>Thanks for the thoughts!
>
>Jason Wharton
>CPS - Mesa AZ
>http://www.ibobjects.com
>
>
>----- Original Message -----
>From: "Aage Johansen" <aagjohan@...>
>To: <IBObjects@egroups.com>
>Sent: Wednesday, November 29, 2000 4:30 PM
>Subject: [IBO] RecordCount
>
>
>> Maybe the best solution for the RecordCount problems would be to remove or
>> rename the RecordCount feature. And, I'm not kidding.
>> 1. During conversion of a BDE project you will get error messages so you
>> will have to fix the problem.
>> 2. You should avoid the RecordCount like the plague, and if you really
>need
>> an estimate of <number of records> you do a 'select count ...'. When you
>> use a where clause (just counting a small part of the table) performance
>> will probably be tolerable. Give your users a choice: great performance
>or
>> not-so-great performance. Or, just say no! to <number of records> ...
>>
>> Regards,
>> Aage J.
>>
>>
>>
>>
>>
>
>
>
>
>
>