The best way to handle look up tables

  • I am working on an ADP project with SQL 2000, my clients will be connecting mainly through WAN. I have large look up table where users must select a value from (user must select a city code from world cities), which slows down the performance of the application. Any thoughts about best practice to do this?

  • How large is it ? Maybe you could load it into an array in your frontend and pass the selected value back to database for processing ?







    **ASCII stupid question, get a stupid ANSI !!!**

  • The table is big as it contains all airports in the world. I am a beginner, so can you tell me how to that (create an array). I am using access as a front face?

  • Sherif - can you break up your lkup table into several ? Meaning - on the front end you have them select (eg.) continent - then display a list of countries - then when they select country you pass this to your lkup table and display only the airports pertinent to the selected destination ?!?!

    Could be one way of doing this!!!







    **ASCII stupid question, get a stupid ANSI !!!**

  • Unfortunately, this can not be done as the user must enter sometimes more than ten airports in one form and the way the airport codes are arranged makes it very difficult to break them in categories

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply