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.

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

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]

Thanks Tim & Roy for your kind answers!