READ and WRITE will still work with all chars. The problem you would have would be that you will not be able to access any of the data via dynamic record methods. In other words, instead of saying REC<5,1> which would access the 1st value of attr 5, you'll need to find the length of the record and proceed byte by byte looking for a byte or bit sequence that will indicate you've found the end of a field and then pull that out with REC[STARTING.BYTE,NUMBER.OF.BYTES.TO.PULL] or something like that.
I've had to do this with COBOL records sent to me from another server in the past. Loads of fun. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Robert Gisi Sent: Tuesday, August 24, 2004 10:38 To: [EMAIL PROTECTED] Subject: [U2] Data Security I understand from IBM that there is a problem storing Encrypted data in a Unidata database because some of the Encrytpion characters are in conflict with our restrictive characters "Multi-values" ,"Sub-values" and others. So how is this issue being resolved in the user community? Please feel free to email me directly since I am aware this is a sensitive subject. I have an urgent need of a resolution . ------- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/
