Discussion:
Invalid index descriptor
(too old to reply)
Mark
2008-10-01 05:18:36 UTC
Permalink
Ooops, the expression upper(7last) does not work. Just 7last does work.

Thanks,
Mark
I have 2 fields in a table - 7last and 7first (I need to start each field name with a number for various reasons).
I try to construct an index in the designer with the expression =
LEFT(upper(7last-7first)+space(45),45), this to always get the same length of this value for the index.
I keep getting invalid index descriptor, and cannot create the index. I even tried another version -
upper(7last-7first) and got the same error.
But just the expression upper(7last) works fine.
Anyone know what I am doing wrong?
Thanks in advance,
Mark
unknown
2008-10-01 07:34:17 UTC
Permalink
On Wed, 01 Oct 2008 01:14:28 -0400 Mark
Sender: Mark <***@NOSPAM.com>
wrote the following in:
Newsgroup: dbase.programming
I have 2 fields in a table - 7last and 7first (I need to start each field name with a number for various reasons).
I try to construct an index in the designer with the expression =
LEFT(upper(7last-7first)+space(45),45), this to always get the same length of this value for the index.
I keep getting invalid index descriptor, and cannot create the index. I even tried another version -
upper(7last-7first) and got the same error.
But just the expression upper(7last) works fine.
Anyone know what I am doing wrong?
See the OLH on 'Table designer fields':

"Name is the name of the field (up to 31 characters for dBASE Plus). You can enter letters, numbers,
and underscores, but no other characters. The first character must be a letter. dBASE Level 7,
Paradox, and most SQL tables allow spaces in field names."


Although the table designer allows you to design tables having fieldnames beginning with a digit you
will sooner or later get into trouble, such as in this case :-)


Ivar B. Jessen
Mark
2008-10-01 13:26:48 UTC
Permalink
Ivar,

Guess I need to go back to the drawing board. I just need a number in every field name, so will have to move it to the end I guess.

Thanks for the info.

Mark
Post by unknown
On Wed, 01 Oct 2008 01:14:28 -0400 Mark
Newsgroup: dbase.programming
I have 2 fields in a table - 7last and 7first (I need to start each field name with a number for various reasons).
I try to construct an index in the designer with the expression =
LEFT(upper(7last-7first)+space(45),45), this to always get the same length of this value for the index.
I keep getting invalid index descriptor, and cannot create the index. I even tried another version -
upper(7last-7first) and got the same error.
But just the expression upper(7last) works fine.
Anyone know what I am doing wrong?
"Name is the name of the field (up to 31 characters for dBASE Plus). You can enter letters, numbers,
and underscores, but no other characters. The first character must be a letter. dBASE Level 7,
Paradox, and most SQL tables allow spaces in field names."
Although the table designer allows you to design tables having fieldnames beginning with a digit you
will sooner or later get into trouble, such as in this case :-)
Ivar B. Jessen
Mervyn Bick
2008-10-01 08:32:07 UTC
Permalink
I have 2 fields in a table - 7last and 7first (I need to start each
field name with a number for various reasons).
As Ivar has pointed out, this is a no-no for .dbf files although a SQL
RDBM such as Firebird or MYSQL, might be more tolerant. One would,
however, need to check the documentation.

If you care to share some of the reasons you feel you need to start field
names with a digit perhaps someone may be able to suggest alternatives.

Mervyn.
Mark
2008-10-02 14:31:35 UTC
Permalink
Mervyn,

Need numbers in field names for rather complex design and documentation reasons. I have simply changed the number to the last instead of the first position.

Thanks,
Mark
Post by Mervyn Bick
I have 2 fields in a table - 7last and 7first (I need to start each
field name with a number for various reasons).
As Ivar has pointed out, this is a no-no for .dbf files although a SQL
RDBM such as Firebird or MYSQL, might be more tolerant. One would,
however, need to check the documentation.
If you care to share some of the reasons you feel you need to start field
names with a digit perhaps someone may be able to suggest alternatives.
Mervyn.
Loading...