Hi,

I am using two table in a master-detail relationship.

1. Table (Recipients):

RecipientsID: integer; (PrimaryIndex)
Name: VarChar
....

2. Table (Addresses);

AddressesID: integer; (PrimaryIndex)
RecipientsID: integer; (Index IDX_RecipientsID)
MailAddress: VarChar;
OrderID: integer;
....

There is an index on RecipientsID in order to link Table2 to Table1. Now
the problem:

Since I want to order the records of Table2, I add the field "OrderID"
to IDX_RecipientsID. When doing so, no record is shown in the
detail-table. What is the problem here?

Thanks Uli.

Uli


Without seeing more all I can do is guess so here goes:

1. You altered the index to OrderID rather than altering it to  RecipientsID;OrderID
2. You altered the index to OrderID ;RecipientsID rather than altering it to  RecipientsID;OrderID
3. The master-detail link somehow got reset
4. There's a bug in ElevateDB

Roy Lambert [Team Elevate]

Roy,

> 1. You altered the index to OrderID rather than altering it to  RecipientsID;OrderID

No.

> 2. You altered the index to OrderID ;RecipientsID rather than altering it to  RecipientsID;OrderID

No.

> 3. The master-detail link somehow got reset

Not in design mode - I checked that.

> 4. There's a bug in ElevateDB

Tim will tell us. I can't imagine that such a construction is not
allowed in EDB.

Regards Uli

Uli,

<< There is an index on RecipientsID in order to link Table2 to Table1. Now
the problem:

Since I want to order the records of Table2, I add the field "OrderID" to
IDX_RecipientsID. When doing so, no record is shown in the detail-table.
What is the problem here? >>

I'm not sure - could you send me the database catalog along with the two
tables ?

Thanks,

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim

> I'm not sure - could you send me the database catalog along with the two
> tables ?

Sure.

Thanks Uli

Uli,

<< Sure. >>

Thanks.  The problem was that the Addressen table's indexes were corrupted,
and a repair fixed the problem.  Was the creation of the index interrupted
at all ?

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

> The problem was that the Addressen table's indexes were corrupted,
> and a repair fixed the problem.

OK, I did the repair here and it works fine now.

 Was the creation of the index interrupted
> at all ?

No, everything just normal. Generally asked: what can cause a corrupt
index and how can it be detected?

Thanks Uli

Uli,

<< No, everything just normal. Generally asked: what can cause a corrupt
index and how can it be detected? >>

I'll do a dump of your indexes (pre-repair) and see what they looked like.
Then I can comment further on what may have been the cause.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

> I'll do a dump of your indexes (pre-repair) and see what they looked like.
> Then I can comment further on what may have been the cause.

Thanks a lot.

Uli

Uli,

<< Thanks a lot. >>

Okay, I've found the issue and a fix will be in B13 very shortly.  There was
a change in the last build or so that broke the alteration of indexes
(especially dropping columns from an existing index), but actually it was a
good thing because the way it was working was a recipe for a bug sooner or
later.

--
Tim Young
Elevate Software
www.elevatesoft.com