>>Do I understand that varbinary() would have to be mapped to char(binary) type field in VFP?. And I am not sure that it would work with cursor adapter via ODBC.
You could try easily enough.
My recollection is that the base SQL Server ODBC may not recognize newer SQL Server field types, but maps some of them fortuitously in VFP; whereas the newer ODBC drivers may recongnize newer field types but context is lost in translation to VFP, with the most glaring example being VARCHAR[MAX]. So BINARY or VARBINARY may be just fine when you try with whatever version of ODBC you're using.
Unless you control ODBC at your clients, another option is to do a CAST in your query to a field type that is processed correctly.
"... 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
