Hi

I have started to get the following error whenever I try to run a 'DELETE FROM ' on one
particular table:

ElevateDB Error #601 The table EDAWARC is corrupt (Invalid index page number specified for
retrieval from cache)

I have attached copies of the table files.

Note, I can run a repair on the table successfully but still seem receive this error.


Thanks in advance.

Which version are you running? This was a problem in (I think) V1 but has been cured for ages.

Roy Lambert

Roy Lambert wrote:

Which version are you running? This was a problem in (I think) V1 but has been cured for ages.

Roy Lambert


I'm using Version 1.09.

RB wrote:

Roy Lambert wrote:

Which version are you running? This was a problem in (I think) V1 but has been cured for ages.

Roy Lambert


I'm using Version 1.09.

Sorry, forgot to state that I've got version 1.09 build 1.  Can you tell me in what
version of the database has this problem been resolved?

RB


The one I was thinking off was

http://www.elevatesoft.com/incident?action=viewaddr&category=edb&release=1.03&type=f&incident=2306

so it doesn't look like that was it. I don't know Tim's policy with respect to fixing bugs as far as V1 goes so my best advice would be to upgrade to V2.

Roy Lambert [Team Elevate]

RB


The one I was thinking of was fixed c1.03.

There were some other 601 errors the latest of which was fixed ion 2.02b7.. ElevateDB is currently at 2.02b8

Roy Lambert

Roy Lambert wrote:

RB


The one I was thinking of was fixed c1.03.

There were some other 601 errors the latest of which was fixed ion 2.02b7.. ElevateDB is
currently at 2.02b8

Roy Lambert


Thanks Roy.

I've e-mailed Tim asking what my options are but going with what you're saying, the only
option is to rebuild my application with the latest EDB version?

RB


I can't answer for Tim, but if you either have, or have to take out a support contract, it would make sense to move to the latest version. I can't remember any issues moving up to V2.

Roy Lambert [Team Elevate]

ps

I see looking at your website the Eclipse Group are into recruitment, since that's my "day job" - how's it going?

<<I can't answer for Tim, but if you either have, or have to take out a support contract,
it would make sense to move to the latest version. I can't remember any issues moving up
to V2.>>

We did have a support plan but it recently expired.  I can download EDB Manager 2.02 b8 -
just to prove that my issue will be resolved with an upgrade to the latest version - can I
not upgrade to the latest version of EDB Manager and run the 'DELETE FROM ' SQL on the
table in question?

<<I see looking at your website the Eclipse Group are into recruitment, since that's my
"day job" - how's it going?>>

Recruitment is done through our subsidiary company, HRGO IT Recruitment Limited, but it's
not something I'm involved with.

Cheers
RB

RB

>We did have a support plan but it recently expired. I can download EDB Manager 2.02 b8 -
>just to prove that my issue will be resolved with an upgrade to the latest version - can I
>not upgrade to the latest version of EDB Manager and run the 'DELETE FROM ' SQL on the
>table in question?

That would certainly do the trick since EDBManager is "just" an application written with ElevateDB.

Roy Lambert [Team Elevate]