Structure of Sailors.mdb

Introduction and Objective

Sailors. mdb supports a hypothetical web site for competitive sailors. The web site includes pages to notify sailors of upcoming regattas, changes in rules, reports on past regattas, and personalized pages based on each sailor's interests. Additional features allow the posting and statistical analysis of regatta results and the ranking of sailors.

Vocabulary and Business Rules

Sailors, in this database are people who race sailboats. These people have the normal personal information such as names and nationalities, as well as an assigned professional class, which reflects their commitment and accomplishment in the sport of yachting. The most skilled sailors, those of Olympic caliber, are rated Professional Class 1 while those who compete at an amateur level are class 3.

Boats are owned by Sailors. A boat has a name and an identifying sail number. Every boat is of a boat class.

A Boat Class is a group of boats of the same shape, sail area and hull size, thus ensuring an even competition among the sailors. Sailors generally race in one class only and thus are not interested in information for boats of other classes.

Sailors race under the aegis of yacht clubs, the organizations which typically sponsor regattas. Yacht clubs have an identifying flag called a club burgee, may have a web site, and each year a yacht club has a meeting at which time information for the season is disseminated. Larger boats are limited to sailing from clubs with a crane to hoist the boat from its trailer to the water.

Competitions generally consist of a series of races (typically 3 to 10), which together constitute a regatta. Based on the results of regattas, sailors are ranked each month from first (most skilled) to 20th (least skilled). Appendix A

Where to Download

This database, in Access format, is available from the Wrox site. The procedures to create the queries for Microsoft SQL Server are also available from the same site in the file Sailors. sql. The end of this appendix lists the information to create the structure of the database by hand.

Structure and Relationships of Tables

The Sailors database contains five tables. There are no relationships permanently created, they are created in queries as needed.

People Table Sailors are listed in the People table; each person is a record. The People table can be related to the Clubs table and to the boats table, since each sailor is a member of a club and most sailors own boats. In addition, the People table can be related to the Rank table. As in all tables of this database there is an ID field with a data type of autonumber. To keep the database small for the download, there are only twenty sailors.

Boats Within the Boat table each record is a boat. The boats can be related to the People table by the PeopleiD as well as the Boat Class table.

BoatCiass This table has only a few records, each representing a class of boats. It can only be directly related to the Boats table. Since all the boats of a given class have the same length, weight and sail area, this information is kept only in the Boat Class table. In our simple example there are just three classes.

Rank Each record in the Rank table represents one sailor in one month of one year. Fields hold the sailor's ID as well as the rank number. This database covers the four months from December 1999 to March 2000.

Clubs Each yacht club holds a record in this table. In addition to contact information, this table holds data for the URL of the club's home page. An image of the club burgee (flag) is held in two places, a file on the server and in a BLOB field in this table. Overview of Queries One group of queries, those beginning with qAll, merely list the records of the table. An exception is the qAllRankings query, which joins the People, Clubs and Rank tables to create a useful recordset for reporting the standings.

A second group of queries begins with qparm. These are for demonstrating the use of passing parameters through the ADO command object. This group includes the qparminsert queries, which are called to append records to tables. 742 Structure of Sailors.mdb

Structure of Tables

Table Field Name Field Type Field Size Notes

Boat Class ClassiD AutoNumber 4 Attributes: Fixed Size, Auto- Number (Long) Increment

ClassName Text 50 ClassLength Number (Long) 4 ClassWeight Number (Long) 4 ClassEntered Date/Time 8 Format: Long Date

Boats BoatsiD AutoNumber 4 attributes: Fixed Size Number (Long) Auto-Increment

BoatName Text 50 Boatel ass Text 50 BoatLaunched Date/Time 8 BoatCertified Yes/No 1 BoatNote Memo Boat Photo OLE Object BoatValue Currency 8 Decimal Places: Auto Format: $#,##0.00;($#,##0. 00)

743 Appendix A

Table Field Name Field Type Field Size Notes

Clubs ClubiD AutoN umber 4 Attributes: Fixed Size Number (Long) Auto-Increment ClubCode Text so ClubName Text so ClubAnnualMeeting Date/Time 8 ClubDues Currency 8 Decimal Places: Auto Format: $#,##0.00;($#,##0. 00) ClubWWWSite Hyperlink

ClubBurgeeFile Text 50 ClubBurgee OLE Object ClubHasCranes Yes/No 1 ClubMembership Number (Long) 4 ClubNote Memo

People PeopleiD AutoN umber 4 Number (Long)

PeopleNameLast Text 50

PeopleNameFirst Text 50 PeopleDOB Date/Time 8 Format: Short Date PeopleProfessionalClass Number (Long) 4

PeopleClubCode Text 50 PeopleReferee Yes/No 1 PeopleState Text so PeopleView Text 50

744 Structure of Sailors.mdb

Table Field Name Field Type Field Size Notes

Rank ID AutoN umber 4 Attributes: Fixed Size Number (Long) Auto-Increment

SailoriD Number (Long) 4 Year Number (Long) 4 Month Number (Long) 4 Rank Number (Long) 4

Structure of Queries

Query Name Query Details qAllBoatClasses SELECT BoatClass.ClassName FROM BoatClass ORDER BY BoatClass.ClassName; qAllBoatNames SELECT Boats.BoatName FROM Boats; qAllBoats SELECT Boats.BoatClass, Boats.BoatName FROM Boats ORDER BY Boats.BoatClass, Boats.BoatName; qAllClubs SELECT Clubs.ClubName, Clubs.ClubCode FROM Clubs ORDER BY Clubs.ClubName; qAllRankings SELECT People.PeopleiD, People.PeopleNameLast, People.PeopleNameFirst, Clubs.ClubName, Rank.Year, Rank.Month, Rank. Rank FROM (Rank INNER JOIN People ON Rank.SailoriD = People.PeopleiD) INNER JOIN Clubs ON People.PeopleClubCode = Clubs.ClubCode ORDER BY Clubs.ClubName, Rank.Year, Rank.Month, Rank.Rank;

745 Appendix A

Query Name Query Details

qDemoQueryGrid SELECT People.PeopleNameLast, People.PeopleNameFirst, People.PeopleProfessionalClass

FROM People WHERE (((People.PeopleProfessionalClass)=2)) ORDER BY People.PeopleNameLast;

qparmBoats PARAMETERS Class Text; SELECT Boats.BoatsiD, Boats.BoatName FROM Boats WHERE (((Boats. BoatClass )=[Class]));

qparminsertBoat PARAMETERS Name Text, Class Text, Launched DateTime, Certified Bit, Notes LongText, [Value] Currency; INSERT INTO Boats ( BoatName, BoatClass, BoatLaunched, BoatCertified, BoatNote, BoatValue) SELECT [Name] AS Exprl, [Class] AS Expr2, [Launched] AS Expr3, [Certified] AS Expr4, [Notes] AS ExprS, [Value] AS Expr6; qparminsertBoatClass INSERT INTO BoatClass ( ClassName, ClassBoatLength, ClassBoatWeight, ClassSailAreaMainJib, ClassSailAreaSpinnaker, ClassAuthority ) SELECT [Name] AS Exprl, [Length] AS Expr2, [Weight] AS Expr3, [MainJib] AS Expr4, [Spinnaker] AS ExprS, [Authority] AS Expr6; qparminsertPerson PARAMETERS FirstName Text, LastName Text, DOB DateTime, ProfessionalClass Long, ClubCode Text, Referee Bit, State Text; INSERT INTO People ( PeopleNameFirst, PeopleNameLast, PeopleDOB, PeopleProfessionalClass, PeopleClubCode, PeopleReferee, PeopleState ) SELECT [FirstName] AS Exprl, [LastName] AS Expr2, [DOB] AS Expr3, [ProfessionalClass] AS Expr4, [ClubCode] AS ExprS, [Referee] AS Expr6, [State] AS Expr7; qParmSailorRanking PARAMETERS ClubCode Text, Ranking Long; SELECT People.PeopleiD, People.PeopleNameLast, People.PeopleNameFirst, People.PeopleProfessionalClass, People.PeopleClubCode, Rank.Year, Rank.Month, Rank.Rank FROM People INNER JOIN Rank ON People.PeopleiD = Rank.SailoriD WHERE (((People.PeopleClubCode)=[ClubCode]) AND ((Rank.Rank)<=[Ranking]))

ORDER BY Rank.Year, Rank.Month, Rank.Rank;

746 Structure of Sailors.mdb

Query Name Query Details qparmVerifyLogin PARAMETERS FirstName Text, LastName Text, ClubCode Text; SELECT People.PeopleNameFirst, People.PeopleNameLast, People.PeopleClubCode FROM People WHERE (((People.PeopleNameFirst)=[FirstName]) AND ((People.PeopleNameLast)=[LastName]) AND ((People.PeopleClubCode)=[ClubCode])); qranktest SELECT Rank.Rank, Rank. Year, Rank.Month, Rank.SailoriD FROM Rank ORDER BY Rank.Rank, Rank. Year, Rank.Month, Rank.SailoriD DESC; qTestWherein SELECT People.PeopleNameLast, People.PeopleNameFirst, People.PeopleClubCode FROM People WHERE (((People.PeopleClubCode) In ('scow','dsyc')));

747

- Structure of Clothier.mdb

Introduction and Objective

The Clothier database supports an Internet site to manage new items in the inventory of a clothing wholesaler. As the wholesaler contracts to buy clothing from manufacturers, the buyers post the items on the web site so they can be ordered by individual stores.

Vocabulary and Business Rules

An item refers to a given model (design) of clothing. An item is not one piece of clothing, but rather one offering by the wholesaler such as the "Mountain Walker" hiking trousers. Every item belongs to a department, such as Women's Sportswear or Men's Formalwear. In addition, each item has a type such as trousers, shirts, or hats.

Items have a release date and since the wholesaler wants to show clothes as early as possible, they are frequently posted to the site prior to release. A quantity per box helps the sales staff since orders are made in full-box quantities. To make this database simpler we use only one price, the wholesaler's buying price.

This business buys from three vendors. Each vendor has a name and a vendor code.

Where to Download

This database is available from the Wrox site. We make it available in Access97 format, which can also be read by Access 2000. The end of this Appendix also lists the information to create the structure of the database by hand. Appendix B

Structure of Tables and Queries

Items Table Each clothing item (design) gets its own record. However, for this site there is no need to differentiate among the sizes and colors. Fields for ordering are included, such as the price and quantity packed per box so the buyer can estimate delivery costs. A numeric code field identifies the vendor and can be used for joins to the vendoriD field of the vendors table.

Note the clarification in the name of the price field. Many of my students start with fields named price, but most items have at least two prices (buy and sell) and can have many more (discount price, manufacturer's suggested retail price, etc). I suggest that a field named Price is always followed by one or more adjectives describing which price.

Vendors Table This wholesaler buys from several vendors, each of which has its own record in this table. The VendoriD field can be joined to the ItemVendor field of the Items table.

In this simple database there are no stored queries.

Table Data

If you are unable to download the tables (like when I lectured in Ulaan Batar in '94, although my friends in Mongolia now communicate by Email without problem), you can create the structure by hand from the data below.

Table Field Name Field Type Field Size Notes

Items ItemiD Number (Long) 4 Attributes: Fixed Size, Auto- Increment ItemName Text 50

ItemDepartment Text 50

ItemType Text 50

ItemPriceBuy Currency 8 Decimal Places: Auto Default Value: 0 Format: $#,##0.00;($#,##0.00)

750 Structure of Clothier.mdb

Table Field Name Field Type Field Size Notes Items ItemVendor Number (Integer) 2

ItemQtyPerBox Number (Long) 4

ItemDateRelease Date/Time 8

Vendors VendoriD Number (Long) 4 Attributes: Fixed Size, Auto- Increment VendorName Text 50

VendorCode Text 50

751

Profile.mdb Database Schema

The following tables describe the profile. mdb database.

Tables profile

Field Name Data Length Indexed Req. OLen. Description Type fname Text 30 No Yes Yes First Name mname Text 30 No No Yes Middle Name lname Text 30 No No Yes Last Name handle Text 75 No No Yes Nickname usehandle Yes/No No No Use Handle instead of Name in profile phone Text 20 No No Yes Phone Number email Text 100 Yes No Yes Email Address (dup) password Text 20 Yes No Yes Password to (dup) edit profile address Text 100 No No Yes Address

city Text 50 Yes No Yes City (dup) state Text 30 Yes No Yes State (dup) Appendix C

Field Name Data Length Indexed Req. OLen. Description Type

zip Text 20 Yes No Yes Zip Code (dup) country Text 20 Yes No Yes Country (dup) image Text 50 No No Yes Image file name template Integer No No Template Number to use in profile fontstyle Text 75 No No No Font Style for Headings in page fontsize Integer No No Font Size for Headings in page fontcolor Integer No No Font Color for Headings in page bgimage Text 50 No No Yes Background Image for page bgcolor Integer No No Background Color for page linkcolor Integer No No Hyperlink Color for page vlinkcolor Integer No No Visited Hyperlink Color for page alinkcolor Integer No No Active Hyperlink Color for page tblbgimage Text 50 No No Yes Background Image for tables in page tblbgcolor Integer No No Background Color for tables in page

754 Profile.mdb Database Schema

Field Name Data Length Indexed Req. OLen. Description Type textcolor Integer No No Font color for text in page tblborder Integer No No Table Border width for tables in page website Text 100 No No Yes Web Site Address newsletter Yes/No No No Does User want to receive Newsletter? job Text 255 No No Yes Job Description in profile hobbies Memo No No Yes Hobbies in profile

bio Memo No No Yes Biography in profile other Memo No No Yes Additional Comments in profile

BLOBs

Field Name Data Length Indexed Req. OLen. Description Type

fname Text Yes Yes First Name email Text 100 No No Yes Email Address from profile picture OLEObj. No No BLOB picture sound OLEObj. No No BLOB sound (.wav file)

755 Appendix C

Stored Queries

deletetest DELETE * FROM profile WHERE email LIKE 'takempis~hatever.net'; lnserttest INSERT INTO profile ( fname, mname, lname, handle, usehandle, phone, email, password, address, city, state, zip, country, website, newsletter, job, hobbies, bio, other, [image), template, fontstyle, fontsize, fontcolor, bgimage, bgcolor, linkcolor, vlinkcolor, alinkcolor, tblbgimage, tblbgcolor, textcolor, tblborder ) VALUES('Kevin', •c•, 'Spencer•, 'Kevin', FALSE, 'lll-222-3333', •takempisoaol.com', 'hello', 'address', •city', •state', 'lllll', 'USA', 'http://www.takempis.com1 , TRUE, 'Internet Database Programming•, 'programming', 'I was born. I lived. I will die', 'whatever', •none•, l, 'Arial', 2, 29, •rosesbg. jpg', 30, 29, 30, 28, •rosesbg.jpg', 18, 30, 0) paramse/ecttest SELECT profi e . * FROM profile WHERE email LIKE mystr; selecttest SELECT profile.* FROM profile; updatetest UPDATE prof le SET email : 'takempis~hatever.net• WHERE email a •takempisoaol.com';

756 Profile.mdb Database Schema

757

I

Creating a Sailors Database in SQL Server

This section covers the required steps to create the Sailors database in SQL Server and assumes you already have the Access Sailors database on your machine. You will need administrator rights to the SQL Server database that you use, and it is recommended that you have SQL Server installed on your workstation. These procedures have been tested with SQL Server 6.5 and SQL Server 7.0.

We will be exporting the tables and table data from the Access Sailors database to the SQL Server Sailors database. This is by far the easiest method to duplicate the Access database into SQL Server.

Creating the Sailors Database

Start SQL Server Enterprise Manager and expand the databases folder. Right click on Databases and choose New Database from the popup menu. Enter the name of Sailors for the database name and select an initial database size of 5 MB, which is more than enough for this database. Take the default for all other options and click on the Create Now button (or OK button if using version 7).

The database has now been created and we need to set up a DSN next.

Creating the Data Source Name

Chapter 2 stepped you through creating a DSN in detail, so we'll just cover the highlights here with no illustrations. Select the System DSN tab in the ODBC Data Source Administrator dialog and click on the Add button.

In the next dialog, choose Microsoft SOL Server and click the Finish button. Give the DSN a name of SOLSailor and select the server where the version of SQL Server that you are using is installed.

On the next dialog select the option With SOL Server authentication using a logon ID and password entered by the user. Enter the logon ID and password of the account you are using to access the Sailors database on your SQL Server. Click Next to continue. Appendix D

Once you receive the next dialog you may need to change the default database to Sailors, if the logon ID you are using has access to more than one database. Accept all other defaults on this dialog and click the Next button. Accept all defaults on the next dialog and click the Finish button.

The next dialog gives you the option of testing the DSN to ensure you are able to connect successfully. It is always recommended that you test the DSN. Once you have tested the DSN click OK to close the dialog and the new DSN will be set up.

Exporting the Tables

Open the Access Sailors database and click on the Tables tab. Perform the following steps for each table listed. Select a table and right click on it, and choose Save As/Export from the popup menu Gust Export for Access 2000). Click OK on the Save As dialog.

Save As ·- 6 EJ

• 'To an flcternal File or Datab~

W1thn the C,Lrrent Database as

760 Creating a Sailors Database in SQL Server

In the Save Table dialog choose ODBC Databases () in the Save As Type combo box.

Suve Tuhle 'llouiCiuss ' In . · fii:J

File uame: lBoatclass.mclb

save as type :

the 5eU4J J:rogram, cliCk Add~emove, n the Office 97 VaUPack.

Once you click on ODBC Databases (), the Export dialog will appear. Click on OK here without changing the table name.

Exporl iJEJ

Export Boatclass to; OK

cancel n ooe.c Database

761 Appendix D

The Select Data Source dialog will appear and you need to click on the Machine Data Source tab and select the SQLSailor DSN as shown below.

Select DetB Source iJEJ

File Date. Source Me.chme Date. Source j

User System System System Text Files User Visue.J FoxPro De.te.be.se User Visue.J FoxPro Te.bles User Xtreme sample date. System

~ew ..

A Machine Date. Source 1s speCific to this me.chme. e.nd cannot be she.red "User" date. sources e.re specific to e. user on this machine "System" date. sources ce.n be used by all users on th1s machine. or by e. system-wide seMce.

OK Ce.ncel Help

Once you click OK on the previous dialog you will be prompted with the SOL Server Login dialog asking for the password for the user id that was specified in the DSN, as shown here.

De.te. Source: SQLSe.ilor

fi Use Trusted Connection Cancel

.Login 10 !sa Jjelp

£as sword Qptions »

Once you have specified the correct password, click on OK. The table will be created in SQL Server, and the data that exists in the table in Access will be loaded into the new table in SQL Server.

Repeat this process for all tables in the Access Sailors database. Note that it is not possible to do all tables at once, without writing complex code. This code would need to extract the database schema, work out how to use this schema to build tables, and extract data, all within the code.

762 Creating a Sailors Database in SQL Server

763

Active Server Pages Object Model

This appendix offers a handy reference to the Active Server Pages object model, and in each case provides the properties, methods and events for the object, along with their collections.

The Request Object

Together, the Request object and the Response object form the 'conversational mechanism' of ASP. The Request object is responsible for controlling how the user sends information to the server. Using the Request object, the server can obtain information about what the user wants- either explicitly (e.g. through programmed ASP code) or implicitly (e.g. through the ffiTP headers).

Collections Description ClientCertificate Client certificate values sent from the browser. Read Only Cookies Values of cookies sent from the browser. Read Only Form Values of form elements sent from the browser. Read Only QueryString Values of variables in the ffiTP query string. Read Only ServerVariables Values of the ffiTP and environment variables. Read Only

Property Description TotalBytes Specifies the number of bytes the client is sending in the body of the request. Read Only

Method Description BinaryRead Used to retrieve data sent to the server as part of the POST request Appendix E

The Response Object The Response object is responsible for sending the server's output to the client. In this sense, the Response object is the counterpart to the Request object: the Request object gathers information from both the client and the server, and the Response object sends, or resends, the information to the client by writing to the HTTP data stream.

Collection Description Cookies Values of all the cookies to send to the browser.

Properties Description Buffer Determines whether the page is to be buffered until complete CacheControl Determines whether proxy servers are allowed to cache the output generated by ASP Char set Appends the name of the character set to the content-type header Content Type HTTP content type (e.g. "Text/HTML") for the response Expires Number of minutes between caching and expiry, for a page cached on the browser ExpiresAbsolute Explicit date and/or time of expiry for a page cached on a browser IsClientConnected Indicates whether the client has disconnected from the server PICS Adds the value of a PICS label to the pies-label field of the response header Status Value of the HTTP status line returned by the server

Methods Description AddHeader Adds or changes a value in the HTML header AppendToLog Adds text to the web server log entry for this request BinaryWri te Sends text to the browser without character-set conversion Clear Erases any buffered HTML output End Stops processing the page and returns the current result Flush Sends buffered output immediately Redirect Instructs the browser to connect to a different URL Write Writes variable values, strings etc. to the current page as a string

766 Active Server Pages Object Model

The Response interface elements can be divided into groups, like this:

Response Items Description Write, BinaryWrite Inserts information into a page Cookies Sends cookies to the browser Redirect Redirects the browser Buffer, Flush, Clear, End Buffers the page as it is created Expires,ExpiresAbsolute,ContentType, Sets the properties of a page AddHeader,Status,CacheContol,PICS,Charset IsClientConnected Checks the client connection

The Application Object

Each application is represented by an instance of the Application object. This object stores variables and objects for application-scope usage. It also holds information about any currently-active sessions.

Collections Description

Contents Contains all of the items added to the application through script commands StaticObjects Contains all of the objects added to the application with the