 	 there are approximately 100,000 triggers, views, procedures, system tables, etc. - think of them as the duct tape that holds Arctos together.
 	 Arctos is a deeply-integrated system which heavily uses Oracle functionality; it is not a couple tables loosely held together by some
 	 middleware, a stark contrast to any other system with which we are familiar.
+	 ---->
 	<p>
 		Arctos access data are available from Google Analytics - ask any member of the Advisory Committee for access. http://www.google.com/analytics/
 	</p>

			<td><input value="#reln.c#"></td>
		</tr>
	</table>
	* The numbers above represent tables owned by the system owner.
	There are about 85 "data tables" which contain primary specimen data. They're pretty useless by themselves - the other several hundred tables are user info,
	 VPD settings, user settings and customizations, temp CF bulkloading tables, CF admin stuff, cached data (collection-type-specific code tables),

			<td>Number Code Tables *</td>
			<td><input value="#ct.recordcount#"></td>
		</tr>
		---->
		<cfquery name="gb"  datasource="uam_god"  cachedwithin="#createtimespan(0,0,60,0)#">
			select count(*) c from coll_obj_other_id_num where OTHER_ID_TYPE = 'GenBank'
		</cfquery>
