IN THIS CHAPTER
Repeating data on a page
Dreamweaver Technique: Applying a Repeat Region
Selectively showing and hiding areas
Moving from record group to record group
Using Data objects for instant recordset navigation
Dreamweaver Technique: Establishing Recordset Navigation
With the power to access the data of the world — or at least your part of it — comes great responsibility. As a Web page designer, you determine how best to present that information. Not only does this include the surrounding look-and-feel but also how the data itself is structured. How many records should you show at once? One? Ten? All? How should the user navigate from one group of records to another? What should the user see when there are no more records to display? Obviously, there are no definitive answers to these questions; each response must take into account the intent of the page, the type of data involved, and the audience for that data. This chapter can't give you precise solutions for every Web application, but it does give you the tools to devise your own resolutions.
What makes a Web page into a Web application? Connectivity to a data source by itself does not make a Web application — after all, you're merely setting up the possibility for data integration, not actually utilizing it. Some would say that it is the power to programmatically control the display of the data that is at the heart of an application. Dreamweaver handles this conditional ...