Hi,

I recently noticed that there is a RecNo issue after upgrading to one of =
the recent DBISAM builds 4.30 build 6.=20

RecNo behavior is somehow broken. When you select a partial SQL result =
RecNos are no longer sequential.

Example:

Select * from TableX  where (1=3D1)

RecNo sequence:  (correct)
1
2
3
4
5
6

Select * from TableX  where (name like 'F%')

RecNo sequence: (incorrect)
4
12
23
54
55
76

BTW, congrats with new web builder product. Look cool!

All the best
Farshad Mohajeri

"Farshad Mohajeri" <infoAT@fmsoft.net> wrote in message =
news:74DE1831-58AD-40B3-8699-566D521696B2@news.elevatesoft.com...

Select * from TableX  where (name like 'F%')

RecNo sequence: (incorrect)
4
12
23
54
55
76

#############################################

That is correct the query has selected the records as
entered and not in numerical order.
So Recno 4 maybe Fab
Recno 4 to 11 maybe Cab
Recno 12 maybe Fac
and so on.

Try table1.recordcount to get a numerical order.
HTH

Farhad,

<< I recently noticed that there is a RecNo issue after upgrading to one of
the recent DBISAM builds 4.30 build 6.

RecNo behavior is somehow broken. When you select a partial SQL result
RecNos are no longer sequential. >>

You could see this behavior (not new) if you request a live result set
(TDBISAMQuery.RequestLive property is True).  In such a case, the result is
the equivalent of the table plus a filter applied, which can cause the
logical record numbers to skip according to the filtered records.

<< BTW, congrats with new web builder product. Look cool! >>

Thanks very much.

--
Tim Young
Elevate Software
www.elevatesoft.com

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
news:2892E3F8-15DB-46CD-949D-6C83F89055C1@news.elevatesoft.com...
> Farhad,
>
> << I recently noticed that there is a RecNo issue after upgrading to one
> of the recent DBISAM builds 4.30 build 6.
>
> RecNo behavior is somehow broken. When you select a partial SQL result
> RecNos are no longer sequential. >>
>
> You could see this behavior (not new) if you request a live result set
> (TDBISAMQuery.RequestLive property is True).  In such a case, the result
> is the equivalent of the table plus a filter applied, which can cause the
> logical record numbers to skip according to the filtered records.
>

Yes, I see this now.

Thanks