LOL...so back to the remaining question: do you think that non-USA
users might encounter issues if I'm using the binary instead of the
unicode or ansi human readable options? Here they are again from
VFP2C32's help:
* 0 = ansi human readable (38 wide)
* 1 = unicode (76 wide)
* 2 = binary (16 wide)
tia,
--Mike
On 2014-06-11 11:28, Richard Kaye wrote:
Something in the thread about the combo behavior being affected by the
\ so I misinterpreted.
I didn't really think you were presenting users with that binary hash
in a dropdown combo. Although if you were then I'd say we have a new
addition to Whil's User Hostile Interfaces presentation... ;-)
--
rk
-----Original Message-----
From: ProfoxTech [mailto:[email protected]] On Behalf Of
[email protected]
Sent: Wednesday, June 11, 2014 11:12 AM
To: [email protected]
Subject: RE: Interesting GOTCHA from 16-byte binary key
They're not displayed...they're all internal. What gave you that
impression? No, the 'dirty' feeling came from large field sizes for
keys. I didn't want the tree to be bloated. I liked the idea of the
smallest sized index field I could have (hence why I changed from 38
to the 16-wide one).
[excessive quoting removed by server]
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
