Allowing multiple choices of data elements enables people to customize views of your data and adds value to your applications. In this sample code, user inputted choice(s) are added to the basic sql statement to draw them from the db. Since the input from the dropdown menu comes through comma delimited it is simply written into the statement without modification. Two simple for next loops determine which elements are part of the record set and displays them accordingly.
In depth article on showing records in a page by page fashion with 'first page','next','back' and 'last page' links at the bottom to navigate through the records. Sample code and database available for download. Online demo also available.
Storing frequently used lookup data in a database is a great idea (e.g. order status codes, state names, etc.) that saves tremendous amounts of time in design and maintenance. However, retrieving that data from the database every time it is needed is very inefficient. This article describes how to use Application variables to cache frequently used lookup data in memory to achieve lightning fast access times.
Providing search capabilities to a db enables users to query on whichever element you target them to. However allowing users to target which portion of the db they would like to query gives extra value. In this example, utilizing our db of US States (state, statename, and capital) the user can search in any of three fields (by dropdown menu input) rather than the application targeting one specific table element. Note: The db only has 50 observations in it, so it is better to search on single or double letter combinations.
Outputting data from two tables is almost as easy as displaying from one. This example utilizes two
tables with state information on them. The first table (state_order) contains state abbreviations (state), state names (statename) the year each state was admitted into the union (year) and the numeric order they entered in (entered). The second table (state_capitals) contains state abbreviations (state), state names (state) and state capitals (capital). The where statement looks to make a match on the field that each table has in common to ouput the correct capital with all the info from the state_order table.
Multiple level select boxes tackled with hierarchical data! This sample illustrates the concept using a hierarchy consisting of geographical region, country, and state data. The code expects a system DSN by name "Hierarchy" and accesses the database using the user id "sa" with a blank password. The database is created in SQL Server 7.0.
This is a quite extensive tutorial on creating your first relational database application. Broken into four different lessons, it covers theories of relational databasing, defining and linking tables, connecting your database to your Web server, SQL, VBScript, and the ActiveX Data Objects (ADO, 2-D arrays, ASP stuff, how to make it work with HTML forms, and more.