I notice that the DecodeBase64 function does not have the optional second parameter. I assume it's smart enough to ignore them in text that has been encoded with carriage returns?
On 4/18/06, Mark Nutter <[EMAIL PROTECTED]> wrote: > You're better off using EncodeBase64 and DecodeBase64. Just be > aware: when you call EncodeBase64, there's an optional second > argument for how often to insert carriage returns (every 72 > characters by default, I believe). If you're storing SaveInfo > strings in a database you'll be ok, but in a text file the > embedded carriage returns can truncate your SaveInfo string. Set > the second argument to zero and you'll be ok. _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives of this list here: <http://support.realsoftware.com/listarchives/lists.html>
