>>We have varchar(max) columns coming OK through SQL Pass-Through. I think there is a setting needed for this, though.
You can use CURSORSETPROP('MapVarChar', .T., 0) that (counter-intuitively) enables varchar mapping at the session level for subsequent selects... but still gets varchar(max) wrong. So unless your solution relies on the older non-native client ODBC drivers, I'm all ears!
Meanwhile Remote Views have always allowed you to map fields including varchar(max) fields to memo, or you can cast to TEXT in your SQL that also does the trick.
"... They ne'er cared for us
yet: suffer us to famish, and their store-houses
crammed with grain; make edicts for usury, to
support usurers; repeal daily any wholesome act
established against the rich, and provide more
piercing statutes daily, to chain up and restrain
the poor. If the wars eat us not up, they will; and
there's all the love they bear us."
-- Shakespeare: Coriolanus, Act 1, scene 1
