Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM General » View Thread |
Messages 1 to 4 of 4 total |
V3>V4: locate (specific case) |
Wed, Oct 21 2009 8:50 AM | Permanent Link |
"Alessandra" | In our app, with 3.30 we used to
mytable.locate('name;visible',vararrayof([partialname,true]),[locaseinsensitive,lopartialkey]) and the results were correct. If partialname was "abc" the locate found the record (suppose): name="abcde" + visible="true" Now with v4 this type of locate doesn't work anymore only if name is "abcde" it gives back true, otherwise it gives back always false. It seems that the partialkey doesn't work anymore in case of multiple fields. Is there a workaround? Thanks |
Wed, Oct 21 2009 5:12 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Alessandra,
<< In our app, with 3.30 we used to mytable.locate('name;visible',vararrayof([partialname,true]),[locaseinsensitive,lopartialkey]) and the results were correct. If partialname was "abc" the locate found therecord (suppose): name="abcde" + visible="true" Now with v4 this type of locate doesn't work anymore only if name is "abcde" it gives back true, otherwise it gives back alwaysfalse. It seems that the partialkey doesn't work anymore in case of multiplefields. >>Are you trying to use loPartialKey across multiple fields ? If so, then no,that won't work with V4 since it only does a partial comparison on the*last* field specified, and the last field specified must be a string field.--Tim YoungElevate Softwarewww.elevatesoft.com |
Wed, Oct 21 2009 11:16 PM | Permanent Link |
"Alessandra" | Tim Young [Elevate Software] wrote:
> Are you trying to use loPartialKey across multiple fields ? If so, then > no,that won't work with V4 since it only does a partial comparison on > the*last* field specified, and the last field specified must be a > string field ok Tim, moving the string field to the last position now everything works as before. These little undocumented changes are getting me mad ) Thanks a lot for your support! |
Thu, Oct 22 2009 11:48 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Alessandra,
<< ok Tim, moving the string field to the last position now everything works as before. These little undocumented changes are getting me mad ) >> I think that change was done to be more compatible with how Locate was supposed to work (ala BDE and TTable), but it's hard to remember now since it was several years ago. -- Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Tuesday, April 23, 2024 at 08:10 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |