Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM General » View Thread |
Messages 1 to 4 of 4 total |
Vista and SetRange() |
Mon, Feb 5 2007 7:25 AM | Permanent Link |
Bill Edwards | Windows Vista, DBISAM 3.30, Delphi 7.
I am testing a non-c/s app on Vista and noticed a problem with SetRange(). For example, assuming a secondary index of "Branch, Name", SetRange( [ABranch], [ABranch] ) returns no records, whereas SetRange( [ABranch,Name1], [ABranch,Name2] ) returns the desired result (as it should). I don't know if DBISAM 4.xx behaves the same as I don't currently have it installed. |
Mon, Feb 5 2007 9:51 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Bill,
<< I am testing a non-c/s app on Vista and noticed a problem with SetRange(). For example, assuming a secondary index of "Branch, Name", SetRange( [ABranch], [ABranch] ) returns no records, whereas SetRange( [ABranch,Name1], [ABranch,Name2] ) returns the desired result (as it should). I don't know if DBISAM 4.xx behaves the same as I don't currently have it installed. >> We don't have a working Vista test machine up and running yet, so I can't test this directly. However, I still can surmise that Vista shouldn't have any bearing on a SetRange unless you're using a non-"ANSI Standard" locale for the table. Is that the case here ? -- Tim Young Elevate Software www.elevatesoft.com |
Tue, Feb 6 2007 8:25 AM | Permanent Link |
Bill Edwards | "Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote:
We don't have a working Vista test machine up and running yet, so I can't test this directly. However, I still can surmise that Vista shouldn't have any bearing on a SetRange unless you're using a non-"ANSI Standard" locale for the table. Is that the case here ? ------------ Tim, Locale is "English(US)" on all tables and machines. I did some further testing in DBSYS (Ver 3.30 and 4.xx): the routine fails with V3.30 (but works when app runs in Vista's XP SP2 Compatibility Mode), and works in all cases with V4.xx! So, I can 1) convert my customers to V4.xx, 2) have them run the app in Compatibility Mode or 3) threaten that if any of them goes near a Vista machine, I do a Jack Bauer on 'em ... Thanks, Bill |
Tue, Feb 6 2007 6:42 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Bill,
<< Locale is "English(US)" on all tables and machines. I did some further testing in DBSYS (Ver 3.30 and 4.xx): the routine fails with V3.30 (but works when app runs in Vista's XP SP2 Compatibility Mode), and works in all cases with V4.xx! So, I can 1) convert my customers to V4.xx, 2) have them run the app in Compatibility Mode or 3) threaten that if any of them goes near a Vista machine, I do a Jack Bauer on 'em ... >> It sounds like we're making some assumptions with the collations in 3.x that we fixed in 4.x, which is quite possible. All in all, EDB is your best bet in terms of future-proofing your application. However, it also might be easier to just do 1) or 2) in the interim. -- Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Saturday, May 4, 2024 at 12:54 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |