Committing a JUnit test that recreates the problem and a corresponding fix
that works around it. Seems like there is a deeper problem here as the
use of the zero-length array could cause a similar problem elsewhere, but
this should fix the main problem.

We added a column to the MS Access db and schema to create data needed
to replicate the issue.  The schema we're committing will only work with
the Access DB attached, so it will need to be genericized.