Ed Leafe wrote: > On Jan 10, 2007, at 11:10 AM, Brian Snipes wrote: > >> Some ( okay, most ) of this is stuff I don't want to think about >> right now but didn't this update fail because of the extra >> apostrophe in the center? > > Sure, because the code treated the field as plain character, when it > was in fact hexadecimal. The hex bits worked out to an ASCII > apostrophe, so that's what was sent.
um, saying "it is hex" is inaccurate. I kinda know what you are getting at, but the way you phrased it is closer to what I want than what currently is. So I don't want anyone (yourself included) to think what I want already exists if it doesn't. fact: it is a 128 bit number. That works out to 16 bytes. It can be represented in hex, but in the context of dabo, my app and this thread, it is not. It is represented in hex in other environments. In the error message I posted, it was being represented as a string of chars. one of those chars is indeed an apostrophe, which is probably screwing up something. As far as I can tell, none of the modules or code we are working with will render? the 16 bytes as the typical dashed hex representation. and there for I doubt I can send a 36 char dashed hex string and expect it to be converted back to 16 bytes. Carl K _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
