×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Since a save of the object.data is not done at a row level, the
speculation that row.data is not being copied into the save file data
must be incorrect. The more likely scenario is that for those data
types, the /externally manifest/ buffer size [e.g. by DSPFFD] for the
field does not reflect the true internal buffer size.
It would seem _more likely_ that the UNDEL2 code has a defect in its
attempt to reverse engineer its access to the data.
The design for those data types was [not the way I would have done
it,] such that, in order to ease access to the languages in a timely
fashion, the request to the database engine for field layouts would
offer up a false definition of the data -- an obfuscation of the truth,
to insulate the caller from reformatting requirements. A seemingly
direct access to the data is in fact indirect, involving an implicit
cast to a character string in the format [DATFMT() specification]
defined to either the job or the query requester. Thus the data is
available directly in human-readable form, rather than the access method
having to request a cast from the internal data representation or
reformat by edtcde/edtwrd [as is done for numeric types].
Regards, Chuck
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
