>> A guid is always 16 bytes. So you could grab the 16 bytes and
encrypt those.
I think what you're working with is an ASCII representation of those
bytes, in HEX. When databases don't support a varbinary
type of guid type to store the 16 bytes in, you're doomed to use the ascii
representation.
WHat's odd is that 16bytes in hex is always 32characters tops. So
it's beyond me why they reserved 30 positions, not 32. 30
positions for a guid is absurd and not enough to store the value. <<
I would think you ought to be able encrypt 16 bytes and have it fit into 30
bytes, depending on the key size, assuming we are talking a varbinary.
===================================
This list is hosted by DevelopMentor® http://www.develop.com
View archives and manage your subscription(s) at http://discuss.develop.com
