In EDB 2.02 build 10 I can locate within a Clobfield many times successful.

With EDB 2.02 build 11 and build 12 too, I can locate within a CLOB-Field only one time
successful.

Any Ideas?

Ulrich,

<< In EDB 2.02 build 10 I can locate within a Clobfield many times
successful.

With EDB 2.02 build 11 and build 12 too, I can locate within a CLOB-Field
only one time successful.  >>

Could you post an example of the code that you're using along with any error
messages that you're seeing ?  I'm not quite sure what type of operation
you're attempting.

Thanks,

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

here is my example:

Fields:
ID = integer
TEXT = CLOB

Rows:
ID#Text
================
1#a
2#b

Now I take a object of TEDBTable and do the following:

Table.Locate('Text', 'a', []); // that's successfull!
Table.Locate('Text', 'b', []); // returns FALSE since Build 11 (Build 10 and earlier
returns TRUE)

I can also change the order of the statements

Table.Locate('Text', 'b', []); // that's successfull!
Table.Locate('Text', 'a', []); // returns FALSE since Build 11 (Build 10 and earlier
returns TRUE)

The same Problem exists with Table.Lookup first take is successfull and second time fails.




"Tim Young [Elevate Software]" wrote:

Ulrich,

<< In EDB 2.02 build 10 I can locate within a Clobfield many times
successful.

With EDB 2.02 build 11 and build 12 too, I can locate within a CLOB-Field
only one time successful.  >>

Could you post an example of the code that you're using along with any error
messages that you're seeing ?  I'm not quite sure what type of operation
you're attempting.

Thanks,

--
Tim Young
Elevate Software
www.elevatesoft.com

Ulrich,

<< The same Problem exists with Table.Lookup first take is successfull and
second time fails. >>

I'll check it out.  I wasn't aware that we were even allowing a Locate on a
CLOB column.

--
Tim Young
Elevate Software
www.elevatesoft.com

Ulrich,

Okay, the issue is caused by the same problem as this:

http://www.elevatesoft.com/newsgrp?action=openmsg&group=16&msg=9507&page=1#msg9507

and will be fixed in Build 13.

--
Tim Young
Elevate Software
www.elevatesoft.com