Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM General » View Thread |
Messages 1 to 4 of 4 total |
Error "Blob field 'mymemo' not allowed in locate or lookup" |
Sun, Oct 11 2009 8:37 AM | Permanent Link |
"Alessandra" | I got this error with 4.29 using something like:
mytable.locate('mymemo',searchkey,[]) where mymemo in a memo field. In 3.30 the located worked fine. Is this a (undocumented?) change from v3 to v4 ? Is there any workaround? Thanks. |
Sun, Oct 11 2009 9:54 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Alessandra,
<< I got this error with 4.29 using something like: mytable.locate('mymemo',searchkey,[]) where mymemo in a memo field. In 3.30 the located worked fine. Is this a (undocumented?) change from v3 to v4 ? >> Yes, you can't locate on memo fields. If it worked in 3.x, it was completely by accident. If you want to search on a memo field, use a filter instead. -- Tim Young Elevate Software www.elevatesoft.com |
Sun, Oct 11 2009 10:40 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Alessandra
I never used that in any version of DBISAM, and didn't know it was ever allowed. You could probably use a filter or sql to get the record key and then use that to reposition the counter. Roy Lambert [Team Elevate] |
Mon, Oct 12 2009 3:37 AM | Permanent Link |
"Alessandra" | Thanks Tim & Roy for your kind answers!
|
This web page was last updated on Tuesday, September 17, 2024 at 04:19 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |