Mark,
All of our data is ASCII text - so we don't normally need to deal
with Unicode. But we have found one source of NULLs in the data is
from people cutting and pasting into the Notes field in some of the
programs.
I don't know to what extent any of this applies to pure Unicode data.
PL
On Aug 31, 2009, at 3:22 PM, Mark Schonewille wrote:
Being unable to sort unicode data would indeed be a Very Bad Thing.
--
Best regards,
Mark Schonewille
Economy-x-Talk Consulting and Software Engineering
http://economy-x-talk.com
Download Snapper Screen Recorder at http://snapper.economy-x-talk.com
On 1 sep 2009, at 00:11, Paul Looney wrote:
General information,
Over the past several months we have noticed that version 3.5 of
Rev is much more sensitive to data that contains NULL characters.
Several programs that worked well previously, with the same data,
broke when using Rev 3.5 - or a standalone made from it.
The problem comes when the data is sorted; the sorting drops
records. Adding the following line, before the sort, fixes the
problem for us:
replace NULL with "" in theData --"theData" is whatever variable
contains the data to be manipulated.
We had minor problems with NULLs previously, but 3.5 will drop up
to 80% of our data.
One way NULLs can get into a database is if Unicode text is copied
from another document.
Hope this saves you some time.
Paul Looney
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
