Thank you, that was the point! Sometimes one inherits numbers as dates,
65535 as CCSIDs, DDS-defined files; all as parts of production
applications that one cannot change without difficulties.
When people get a-hold of these systems, they tend to ask "poor"
questions. In this case, the OP even found the answer himself ( and had
the courtesy to post a reply saying he had done so ). IMHO, to dismiss
these questions off-hand was counter-productive.
On 02/15/2014 12:05 PM, Vernon Hamberg wrote:
With a packaged app, you can't change the files - the ISV has done what
they did for reasons, and they handle this stuff in their programs.
So I suggest you use the setting to convert 65535 stuff - there's really
no other choice in your situation, I think.
On 2/15/2014 8:31 AM, Narayanan Pillai wrote:
That work-around is essentially telling a lie to the system, to trick
the system into behaving as one might expect in a particular situation.
However, that same lie may expose ill-effects in other
cases\situations; i.e. in a scenario where the tagged-ad binary-data
should indeed be treated as binary-data, whereby /forced conversion/
will be undesirable.
Pardon the ignorance, how does one go about doing this for a packaged
application, like JDEdwards, for instance?