The following data is from the 2008-2009 NJ State Report Card.

  AJ strikes a backhand in this AP file photo.

In a hotly contested and highly anticipated 16th match of the season, Mark and AJ matched up in what some billed as the hottest tennis match on record.

The match, preceded by copious amounts of trash talking, began where the previous match had left off, with Mark hitting highly precide, topspin enabled forehands and backhands for winner after winner.

Mark took the beginning set 6-3 in fairly convincing fashion.

In a set that very well could be a turning point in the seasonal series, Mark, by his own admission, took his foot off the throttle in a conscious decision to attempt to save energy and coast to a victory. This strategy however was very short-sighted, as A.J., backed by a powerful kick serve, cruised to a second set victory, 6-3.

In a third set that onlookers descrived as scintillating, A.J. completed his match victory by displaying a well oiled ground game, with 2 parts of hustle.

With his victory, A.J. snapped his 2 game losing streak over his bitter rival, and potentially set the tone for the rest of the season.

  Victories By Year

So, you have a long, drawn out form with multiple radio buttons.

So while this is a standard looking series of radiobuttons, the usability is hindered by default since the user must aim and click on the radio button itself.

This is where the label tag comes in.

Using the following code instead:

<table>
  <tr>
    <td style="padding-right: 10px;">
      <input type="radio" name="id" value="1" id="1">
      <label for="1">Value Of 1</label>
    </td>
  </tr>
  <tr>
    <td>
      <input type="radio" name="id" value="2" id="2">
      <label for="2">Value Of 2</label>
    </td>
  </tr>
  <tr>
    <td>
      <input type="radio" name="id" value="3" id="3">
      <label for="3">Value Of 3</label>
    </td>
  </tr>
</table>

This effectively links the textual description of each radio button to the radio button itself, so the user can click on the radio button or the label to get the desired click effect, as follows:

So let’s say you have a SQL Server db that contains 100 tables. You want to know which of these 100 tables contains a column of a certain name without poring through all 100 manually.

Use this syntax:

SELECT * FROM sysobjects
WHERE id IN ( SELECT id FROM syscolumns WHERE name = 'column_name_here' )

This only seems to search the db in current scope, not all the db’s in your particular SQL Server DBMS.

Most sources will tell you that in order to delete a cookie using cfcookie, that you need to set it’s expiry time to ‘NOW’.

<cfcookie name="source_id" expires="Now">

For some reason, this seems kludgy to me. Are the browser and the web server going to agree as to what the meaning of ‘Now’ really is?

I prefer a more concrete approach.

<cfset result = StructDelete(cookie, "source_id")>

No if, ands, or buts here. That cookie is toast. At least at the ColdFusion app server level. The cookie still exists on the users machine. But the app server is unaware of this, since it’s internal representation of the cookie has been destroyed, and won’t be rebuilt again unless the cookie is explicitly reset. To be sure, using both methods in conjunction with one another is a safe bet.