2014.12.11 MSS Code Factory 2.0.12693 SAP/Sybase ASE is going to be pulled from support again

After over a day's work switching over to the use of #tmp tables for Sybase ASE
in order to resolve a database problem, I encountered a new problem with using
non-transactional #tmp table model would be onerous, to say the least, so Sybase ASE
is being dropped from the support list again.  I'm checking in this version of code
in case I ever come up with an idea about how to make it go that I haven't thought of
or tried yet today.

There is a currently a bug affecting updates of OptFullRange for CFDbTest 2.1.
I'll need to do an Eclipse build to trace through to debug that one, and I
don't even have the project created yet so it'll take a bit of time.  This
affects test 0032-UpdateOptFullRangeWithValues.  It is the only test case for
which Sybase ASE is still failing.

The results of all stmt.execute() invocations are now processed, so the
exceptions raised by the Sybase ASE instance for failed invocations of
sp_delete() (including permission denied) are now propagated through
the Java exception hierarchy as they are for processing other statements.

The ReplaceComplexObjects test for CFDbTest 2.1 is now passed by
SAP/Sybase ASE 16.0.  I had removed SAP/Sybase ASE from the support
list out of frustration, because it raises exceptions if you modify
any of the tables behind a complex query, invalidating your cursor.
Without that ability, I could not implement DelDep and ClearDep support.

A few days ago I realized this was a situation that could be addressed
through Sybase #tempdb transaction tables.  Instead of cursoring over
the complex query, I now select the complex query into a statement-specific
been a long time since I encountered an issue like this, so it took a
while to remember how to work around it for Sybase.  It has been a long debug
session to get this approach working, fraught with many runtime errors
pointing me to further code tweaking of the database scripts each time.

That leaves the Chain support to be ported from PostgreSQL to
SAP/Sybase ASE after I've debugged this OptFullRange update issue.