On 21.10.2010 14:55, Radovan Antloga wrote: > Yes I agree with your security arguments. But I think you could > remove property in next release and document this as incompatible > change. If you like to stay compatible you can IFDEF property from > published to public in Unicode compilers. I can easily do this, but I am not sure how this would confuse users upgrading to Unicode Delphi versions. Any other opinions on this list? > It would be less confusing because it is expected for published > properties to be stored in DFM. I think so, too, but Embarcadero apparently thinks differently for RawByteString properties. Ralf _______________________________________________ Delphi Inspiration mailing list yunqa@xxxxxxxxxxxxx //www.freelists.org/list/yunqa