Using SQL Fetch with an unknown number of columns

[MEovino@xxxxxxxxxxxxxxxxx]

We have an app that uses a dynamically generated SQL statement to query out
a set of records.  Files, fields, sorts, etc. are stored in a file, so we
have no way of knowing what the recordset will look like at compile time.
Because of this, we're having problems using Fetch in any sort of
meaningful way.  We know how to Fetch into a DS or a bunch of variables,
but both seem to require knowing what the recordset looks like at compile
time.  If we have more variables in the Fetch Cursor Into statement than we
have in the recordset, will this be a problem?

All we want to do is dump the recordset into a work file so we can export
that out to a PC file.  Unfortunately we're still on V5R1, so we don't have
Create Table As.

Mike E.