Francois Piette wrote: >> Regarding the hard coded boundary strings I suggest to >> make them (or parts) component properties. > > Would be a good idea to create a property XMailer with that string. > The default value would be the current value. Some trick should be > used so that the correct component version is used even if the > property is serialized because the component has been dropped on a > form. I think of a kind of placer holder such as "%VER%" within the > string.
I'm not sure what you mean by "some trick". Do you mean a place holder as visible part of the default published string property, stored in dfm and replaced internally only when headers are built? -- Arno Garrels -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be