2014.09.26 MSS Code Factory 1.11.12416 Service Pack 1

With the changes described below, Service Pack 1 is finally
ready for release and use by the general design and programming
communities.

The Swing GUI prototype has been tested with all six databases.
There were a few problems with the MySQL code, but the other
databases were working as of 1.11.12414.

For starters, I needed to create .bat scripts to install
the database to a MySQL 5.6 instance under Windows 7.  That was
expected, though, as many of the other databases won't run
scripts from Cygwin64 either.

Next up, the sp_create stored procedures weren't populating
the audit columns on insert.  I was surprised to find this as
a problem, as I *thought* I had tested the code under MySQL 5.5
on Linux.  Apparently my testing process wasn't very good.

The last problem was with the read-by-index stored procedures,
or rather with the JDBC code that was invoking them.  There were
some missing commas in the SQL statements, which resulted in
an argument underflow when invoking the read procedures.  Not all
read procedures were affected by this bug.  In particular, it
apparently did not affect any of the CFDbTest 2.0 database tests
as I was able to run those successfully (or as close to it as MySQL
can get), but it did crop up when trying to browse the data
through the CFDbTest 2.0 Swing GUI prototype for MySQL.

The Swing prototype GUI has been modified to rely entirely on
the interfaces that are expected to be provided by the JPanels
and JInternalFrames created through the Factory interfaces.
This allows you to either subclass the components that are
produced by the manufacturing process, or replace them completely
with custom code, according to your needs.  The intent of the
prototype is to provide a "leg up" on developing a GUI, while
taking care of a lot of the "plumbing" required by Swing interfaces.

The prototype GUI was originally developed for the primary purpose
of doing design walk-throughs with users who are likely to be
unfamiliar with data models provided by ERD or UML diagrams, and
to instead give them a visual representation of the data provided
by a Business Application Model.  This goal has been achieved, but
then I realized that by applying the factory/interface metaphors,
the code could be useful in the development of a full user interface,
not just a demo/prototype.