I have a table that is being sent via cursortoxml and then back using xmltocursor. All works well unless I have just one record with a field that is character type, but has a number in it. When that happens, the cursor created is inferred to be numeric. It's hard to predict when this will happen without having a data dictionary to compare to. As a result if I try to copy from the cursor to my destination table, I get data type mismatches.
Is there any way to force cursortoxml and xmltocursor to respect the data type of the original table?
Thanks in advance!
Steve Howie, owner
DaSH Technology
Denver, CO