UpdateAllRecords bug?

[Ruslan Zasukhin]

On 22/10/07 10:26 PM, "jda" <jda at his.com> wrote:

Hi Jon,

> Hi Ruslan,
> 
> Is there a known issue with updateAllRecords.

Not known.
 
> With a fresh db I'm doing this with a cursor:
> 
>   myCursor = myDatabase.SQLselect(query, EVCursorLocation.kServerSide,
> EVLockType.kReadWrite, EVCursorDirection.kRandom)
>      if myCursor <> nil and myCursor.recordCount > 0 then
>              myCursor.Field(fldNames).setString(s)
>      end if
>     myCursor.updateAllRecords
> 
>      result = myCursor.firstRecord -> error
> 
> If there is more than one record on the cursor, this last line gives
> an error. Here's the error if there are 50 recrods in the cursor:
> 
> Segment "51" is wrong. The last segment is "50".

Related to some TEXT field.
 
> The db is now corrupted, according to diagnose.
> Looping through myCursor works, and so I'm using that in my code.
> I can upload a db to Mantis, if you want to see it.

* You have not point version of engine you are using.

* I can recommend try as workaround command.
        UPDATE ... WHERE

* if you use LATEST 3.4 or 3.5b5  engine then yes, please report into
Mantis.


-- 
Best regards,

Ruslan Zasukhin
VP Engineering and New Technology
Paradigma Software, Inc

Valentina - Joining Worlds of Information
http://www.paradigmasoft.com

[I feel the need: the need for speed]