>>Not sure I see how that solves the requirement.
>>
>>The structure of the tables on the back end might now
>>match the field names used in the app.
>>
>>So I would like to get the data back from the DB in the
>>format used in the GUI, so that I can minimize the amount
>>of changes there.
>>
>>The CursorSchema allows me to specify what the result data
>>set will look like, as far as structure, correct?
>
>Yes, but the CursorSchema must match the data types of the fields being returned from the DB. Otherwise, your DB must support CASTing of one data type to another. The order of the field names specified in the schema must also match the order of the field names returned from the DB as well. The field names selected from the DB must match the field names you specify in the CursorSchema.
>
>I thought you were suggesting that the table structures across different DB platforms might differ. If they do not and they are all compatible with each other, then you should have no problems.

With the exception of VFP's Logical data type, most of the data I will work with
should be compatible. If the SQL field is varchar, I can live with it, as it should
map fine to a character field in a VFP table. Same with Int to numeric. At least
thats what I'm hoping. Some of the field names would almost certainly change, but
as long as the data types are compatiable, I can't see any reason using CursorSchema
to get back a desired structure table would be a problem.

But, I've been wrong before....