I have a simple data entry form and one of the fields the user needs to input into is a Ticket# field which is set as a long text but in reality its between 10-15 characters (SQL server has it as nvarchar(255). The ticket number already exists and the user just needs to pick/input the correct one he is working.
I currently have the ticket # as a list box that is pointed to local table that contains all of the tickets. It works but the local table has over 30,000 records so as you can imagine the list box is quite full.
I guess my question is should I maybe do some type of validation where the user inputs the ticket # themselves and have some type of process that validates it against the table with all of the tickets in it to make sure its a good ticket? Or should I just leave it as a list box? It wouldn't be so bad if the user could type "159" and all the values that start with 159 would appear in the list box but its not working that way.
I currently have the ticket # as a list box that is pointed to local table that contains all of the tickets. It works but the local table has over 30,000 records so as you can imagine the list box is quite full.
I guess my question is should I maybe do some type of validation where the user inputs the ticket # themselves and have some type of process that validates it against the table with all of the tickets in it to make sure its a good ticket? Or should I just leave it as a list box? It wouldn't be so bad if the user could type "159" and all the values that start with 159 would appear in the list box but its not working that way.