Jean - there's some mapping you can do, to handle AND DEFINE nil/null
values. As to 'where' - it sorta depends on WHAT yer using to generate
that recordset. If yer using an odbc driver for DB/2, is possible to
handle it all with the settings on the driver, when INCLUDING the odbc
driver in the 'data connector' with VFP, from INSIDE of the data connector
settings, inside of the database connector thingie. ONCE you have that
set, properly, you can auto-generate the code to create the settings for
the data connector, re-use it if you are using SQL-Pass-Through, prior to
calling the stored procedure.
But I'm grasping at straws here, really..
HTH?
Mondo Regards [Bill]
--
William Sanders / efGroup {rmv the DOT BOB to reply}
Mondo Cool WebHosting -> http://www.efgroup.net/efglunar.html
Mondo Cool DSL -> http://www.efgroup.net/shopfordsl.html
Failing dotNet Project? -> http://www.dotnetconversions.com
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
