Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM General » View Thread |
Messages 1 to 4 of 4 total |
DBISAM RecNo problem |
Thu, Aug 25 2011 5:21 PM | Permanent Link |
Farshad Mohajeri | 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 |
Sun, Aug 28 2011 6:30 PM | Permanent Link |
Rita Tipton | "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 |
Tue, Aug 30 2011 11:31 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@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. << BTW, congrats with new web builder product. Look cool! >> Thanks very much. -- Tim Young Elevate Software www.elevatesoft.com |
Mon, Sep 5 2011 3:12 PM | Permanent Link |
Farshad Mohajeri | "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 |
This web page was last updated on Tuesday, May 7, 2024 at 06:25 PM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |