|
Some folks haven't run into this yet, so it bears politely repeating that this is a FAQ. (Maybe an archive search too!) The problem is not the use of 'B'; rather, it is a misunderstanding of what the documentation means by the use of the word Binary.
Here's the documentation for the null byte map for a trigger: New/Original record null byte mapThis structure contains the NULL value information for each field of the new record. Each byte represents one field. The possible values for each byte are:
midrange.com
'0'
Not NULL
'1'
NULL
Where does it say "Binary(2)" in that text? In any case, a "2B 0" is
actually a 2-byte AND 2-digit binary number, so this is actually one case
where it does NOT fall into that FAQ entry.
however, anything that's 2 bytes is obviously wrong for this definition. Furthermore, the fact that you're using the "B" data type which converts a 2-byte binary (able to store numbers up to 32767) to a 2-digit packed (able to store numbers up to 99) is obviously going to cripple you.
So, it's NOT that the OP misinterpreted "Binary(2)", it's that the "B" data type is the wrong tool for the job.
There isn't a situation where it's the right tool for the job. Never use it.
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.
