Wouldn't it be nice if you could use good-ole SQL language to execute a Select statement
against a set of locally-cached DataTables that you've already retrieved from an underlying
database?

This class does exactly that... it supports a minimal set of SQL SELECT command statements
against a group of ADO.Net DataTables contained in a detached DataSet.  The purpose is to
prevent a round trip to the server to accomplish simple things like what is available with
the JOIN and GROUP BY clauses of the SELECT command.

This is *NOT* a complete SQL Engine... in fact, it's not even a complete implementation of
just the SELECT command. Consequently, there is no support for any DDL statements (ALTER,
CREATE, or DROP) nor any other DML statements (INSERT, UPDATE, or DELETE) nor any DCL
statements (GRANT, DENY, or REVOKE).

The syntax for the SELECT command is designed around the SQL Server 2000 dialect of the SQL
language. There is certainly no claim of compliance with any SQL standard. The most
significant limitation is the rather poor support for SQL Server 2000's huge list of
functions.

Operators, Functions, and Expressions are limited to what is natively supported (or easily
translated) by ADO.Net, namely:

	Comparison: <, >, <=, >=, <>, =, IN, LIKE, IS NULL
	Logical: AND, OR, NOT
	Math: +, -, *, /, %
	String: +
	Wildcards: *, %, []
	Aggregation: SUM, AVG, MIN, MAX, COUNT, STDEV, VAR
	Functions: LEN, ISNULL, IIF, TRIM, SUBSTRING, CONVERT

What *is* supported is SQL statements like the following:

	SELECT Categories.CategoryID, CategoryName, AVG(UnitsInStock) AS AvgUnits
	FROM Products JOIN Categories ON Categories.CategoryID = Products.CategoryID
	WHERE (UnitsInStock > 0) AND (Discontinued = 0)
	GROUP BY Categories.CategoryID, CategoryName
	HAVING (AVG(UnitsInStock) > 30)
	ORDER BY AvgUnits DESC

OK, I'll admit... If you plan on doing any serious SQL work, you might first consider
using a locally-installed copy of Microsoft Desktop Engine (MSDE).  MSDE is well supported
and is free!

Note: This is a demonstration project... not production code.  It has not been thoroughly 
tested in a production environment.  I'd highly recommend you perform your own side-by-side
testing of the output of this DLL and a "live" database.