>>Hi,
>>
>>Is this a known issue (not mentioned in the docs AFAICS):
>>
>>I'm issuing the following:
>>
>>ALTER TABLE Printers ALTER COLUMN DeviceName C(250)
>>
>>There's a regular index on this field (which initially has a length of 40)
>>
>>I get an 'Invalid key length' message box but the field length is altered and *the index is dropped* !
>>
>>Surely it should completely reject the change ?
>
>If you neef the index for anything then ==, yes. Or at least only up to 120/240 chars, depending on your settings.
>If you only need == then you might use a HASH as index. I do this with some memos.
>
>Lutz

Thx. A hash would work but that would need modifying existing code for any searches. With 3K+ users out there I try to avoid that :-}
And, in this case, a 200 character limit should be fine.....