Frog Survey Updates:

1/06/09: mls	frogsurvey.mdb
Moved the non frog survey related tables from frogsurvey.mdb into a new database for the webpages called webpages.mdb. These are the tables that get updated via the fckeditor and displayed via stuff like default.asp/?cid=19.

1/26/09: mls	CheckDate.js
Changed check after "dateparts.length !=3" to return a non-null string in datemsg. Before, it did not set datmsg, but simply put up an alert. This caused the code in observe.asp to try to update the database even when the date was invalid. This would not allow nulls to get into the database, but allow odd dates in the future to be entered.

1/26/09: mls	frogsurvey.mdb
a. "Grey Treefrog" was changed to "Copes Grey Treefrog" in both the DataSighting table and Species table to differentiate it from "E. Grey Treefrog."
b. I updated the  "SpreadsheetForExport" query and queries it uses ("Export_T1 and "Export_T2" to do the following:
i. Do not filter out records where Temp are zero.
ii. Do not create extra records for each species (this was the first change you requested.)
iii. Set Time to "Location Skipped" if it is NULL.
iv. Do not set the "Seen", "Call Index" nor any other field to "S" or "X" if the Time NULL. Thus, what you see is what is in the database. My rational is that if  something is odd in the database, this will give someone a chance to go back and edit the database through the website rather that obscuring the oddity    when the data is exported to a spreadsheet.
c. I saved the old "SpreadsheetForExport" query as "SpreadsheetForExportOld" and queries it used as "Export_T1Old" and "Export_T2Old"

5/13/09: mls	asp/Location.asp
Updated Javascript to make sure that no more than 4 decimal digits are entered for longitude or latitude. The database field is apparently not big enough to hold more than 4.

12/28/09: mls	frogsurvey.mdb
Added Kendall County to the county table