Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 5 of 5 total
Thread Duplicate key error
Thu, Dec 21 2006 10:59 PMPermanent Link

Jerry Blumenthal
Using D4 and DBISam 2.12, I am getting an error 9729 when I do a FINDKEY
  on one of my tables.

The table has only the primary index.  There are only TWO records in
this table at present.  The table is definitely open.  I am looking at
the table in dbsys, and with only two records each with 4 small fields,
you would think that any problem would be glaring out at me but there is
nothing I can see.  RepairTable shows no problems.

What could I be missing?

Jerry



DBISAM Engine Error #9729 Duplicate Key Found in index
Fri, Dec 22 2006 3:30 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Jerry,

<< Using D4 and DBISam 2.12, I am getting an error 9729 when I do a FINDKEY
on one of my tables.

The table has only the primary index.  There are only TWO records in this
table at present.  The table is definitely open.  I am looking at the table
in dbsys, and with only two records each with 4 small fields, you would
think that any problem would be glaring out at me but there is nothing I can
see.  RepairTable shows no problems. >>

FindKey won't raise such an error, it should be occurring on a Post.  Is
that correct ?

--
Tim Young
Elevate Software
www.elevatesoft.com

Fri, Dec 22 2006 4:40 PMPermanent Link

Jerry Blumenthal
Tim Young [Elevate Software] wrote:
> Jerry,
>
> << Using D4 and DBISam 2.12, I am getting an error 9729 when I do a FINDKEY
> on one of my tables.
>
>  The table has only the primary index.  There are only TWO records in this
> table at present.  The table is definitely open.  I am looking at the table
> in dbsys, and with only two records each with 4 small fields, you would
> think that any problem would be glaring out at me but there is nothing I can
> see.  RepairTable shows no problems. >>
>
> FindKey won't raise such an error, it should be occurring on a Post.  Is
> that correct ?
>


Definitely FINDKEY.  here's the code:

  statusbar1.SimpleText := 'findkey= ' +inttostr(n);
  try
  if dbresources.findkey([n]) then begin
    result := dbResourcesName.asstring;
    statusbar1.SimpleText := 'found='+ dbResourcesName.asstring;
    end
  else statusbar1.SimpleText := 'NOT found=';
  except
    statusbar1.SimpleText := 'after findkey error= ' +inttostr(n);
    showmessage('error trying to get resource from link');
    raise;
    end;

The statusbar shows: findkey= 1001

Jerry
Sat, Dec 23 2006 8:29 AMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

Jerry


Is there a chance that the table is in insert mode when you're doing the findkey? That would result in a post being tried and the error generated.

Roy Lambert
Wed, Dec 27 2006 5:29 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Roy,

<< Is there a chance that the table is in insert mode when you're doing the
findkey? That would result in a post being tried and the error generated. >>

Good point.  That is most likely the cause for the Post occurring on the
FindKey.

--
Tim Young
Elevate Software
www.elevatesoft.com

Image