>I have found that autocomplete by default is only working correctly (in my mind at least) if the width of the data is not greater than 30 characters. I tried using autocomplete on a textbox used in getting a folder name. If the folder name was longer than 30 characters, each time the folder was picked a new entry was added to the autocomp.dbf table
. I have noticed that the index created for the autocomp.dbf is UPPER(source+LEFT(data,30))+PADL(count,8). If I change the 30 to let's say 40 then autocomplete works correctly for data up to and including 40 characters. Does anyone know of the ramifications of changing the index on the autocomp table or if I am missing something here?
Since the autocomplete.data is a c(254) field, obviously it can store longer values. The choice of 30 for the index was probably some guesstimate of a good default value - but then you can have your own table with a shorter field, and as long as the index conforms to the same rule of composition, why not create your own autocomplete table(s) with custom index?
