Tim


I'm getting an error. Its not one I've ever seem before

Field index out of range.

By searching the Borland code I eventually found it in DBTables and DBClient. Looking at my code and the table structure I finally figured out that " if lu.Career.FindKey([luContact, luCompany]) then begin" was the problem since there wasn't a compound index of this nature (there are two separate indices using those fields though.

I don't know if its possible, or how much work it would take but it would be nice to have a better error message eg No suitable index exists for those fields.

Roy Lambert

Roy,

<< By searching the Borland code I eventually found it in DBTables and
DBClient. Looking at my code and the table structure I finally figured out
that " if lu.Career.FindKey([luContact, luCompany]) then begin" was the
problem since there wasn't a compound index of this nature (there are two
separate indices using those fields though.

I don't know if its possible, or how much work it would take but it would
be nice to have a better error message eg No suitable index exists for those
fields. >>

It's a standard error message that matches the same message that
Borland/CodeGear has always displayed, although I'm not sure if that's a
ringing endoresement.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim


>It's a standard error message that matches the same message that
>Borland/CodeGear has always displayed, although I'm not sure if that's a
>ringing endoresement.

Believe me it isn't. Had me running in circles a while it was so full of informational content.

Roy Lambert