Autodesk 15606-011408-9300 Developer Guide - Page 113

Controlling the Output, Recordset, Execute, Connection, SQLQuery, <BODY&gt, RSAPN, Owner_Name

Page 113 highlights

The third line creates a variable that holds a SQL statement specifying the database records for houses built in 1963: SQLQuery = "SELECT * FROM Parcel_Data Where Year_Built = '1963'" The last line puts it all together, creating a Recordset object and assigning it to an object variable named RS. Note that Execute is a method of the Connection object, in this case dbConnection. We're using Execute to run the SQL statement we assigned to SQLQuery: Set RS = dbConnection.Execute(SQLQuery) Controlling the Output Now that we have our Recordset object, let's add a block of code that controls how the database output is displayed on the page. This code should appear within , at the location where you want the database output to appear. If you want to display the parcel number, owner's name, and year built, your output code will look like this: Parcel Number: Owner: Year Built: If you're accustomed to client-side scripting, this code might look peculiar. Notice how it is actually two different script tags that operate on HTML code sandwiched in the middle. Let's look at the HTML portion first: Parcel Number: Owner: Year Built: As with ColdFusion, this is standard HTML plus a few variables. ASP variables use the standard ASP script tags (), as well as an equal sign that tells ASP to substitute the actual value for the variable. In this case, the value is a field in your map resource database. For example, RS("APN") is the APN column in the database represented by the RS object you created earlier. Without the accompanying script tags, the HTML would display the APN, Owner_Name, and Year_Built fields for only the first record in the database: Parcel Number: 941-0103-003-01 Owner: James P & Bonnie G Reed Year Built: 1963 Creating Report Scripts with ASP | 113

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208

Creating Report Scripts with ASP
|
113
The third line creates a variable that holds a SQL statement specifying the
database records for houses built in 1963:
SQLQuery = "SELECT * FROM Parcel_Data Where Year_Built = '1963'"
The last line puts it all together, creating a
Recordset
object and assigning
it to an object variable named
RS
. Note that
Execute
is a method of the
Connection
object, in this case
dbConnection
. We
re using
Execute
to
run the SQL statement we assigned to
SQLQuery
:
Set RS = dbConnection.Execute(SQLQuery)
Controlling the Output
Now that we have our
Recordset
object, let
s add a block of code that
controls how the database output is displayed on the page. This code should
appear within
<BODY>
, at the location where you want the database output
to appear. If you want to display the parcel number, owner
s name, and year
built, your output code will look like this:
<%
Do While Not RS.EOF
%>
<P>Parcel Number: <%=RS("APN")%><BR>
Owner: <%=RS("Owner_Name")%><BR>
Year Built: <%=RS("Year_Built")%></P>
<%
RS.MoveNext
Loop
%>
If you
re accustomed to client-side scripting, this code might look peculiar.
Notice how it is actually two different script tags that operate on HTML code
sandwiched in the middle. Let
s look at the HTML portion first:
<P>Parcel Number: <%=RS("APN")%><BR>
Owner: <%=RS("Owner_Name")%><BR>
Year Built: <%=RS("Year_Built")%></P>
As with ColdFusion, this is standard HTML plus a few variables. ASP variables
use the standard ASP script tags (
<%
and
%>
), as well as an equal sign that tells
ASP to substitute the actual value for the variable. In this case, the value is a
field in your map resource database. For example,
RS("APN")
is the APN
column in the database represented by the
RS
object you created earlier.
Without the accompanying script tags, the HTML would display the APN,
Owner_Name
, and
Year_Built
fields for only the first record in the database:
Parcel Number: 941-0103-003-01
Owner: James P & Bonnie G Reed
Year Built: 1963