General information
Category:
Coding, syntax & commands
Craig:
To an extent, my way is doing something similar to yours, in that it is narrowing down the possible records. However, mine does it on the fly, by eliminating whatever doesn't match the user's keystrokes. In general, my tables aren't going to be bigger than a few thousand records, which means my original way would be fast enough. I'm just concerned about our largest customers, who may have up to 300,000 records. You are right that nobody would want to scroll that many records, but I don't want to build different systems for different-sized customers. I also need to allow the end users some leeway, in case they don't have the exact spelling of the person's last name, for example.
Jerry
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only