Hallo Martin, Du schriebst am Wed, 18 Jan 2012 07:52:37 +0100:
> I think using TField.Value and the different TField.as* properties in > OnValidate is OK, there is no need to add a special property for the > purpose. Solely IvankoB must switch his mind. ;-) AFAIR he didn't want a new property either, just opposed to the naming of the holding property for the db-derived "newvalue", which turns old as soon as there's another value to be stored... Anyway, mine was just a suggestion for compromise, I've no problem with either, if I can discern what they mean and how they're to be used. For my part, you can keep'em as is. ;-) -- (Weitergabe von Adressdaten, Telefonnummern u.ä. ohne Zustimmung nicht gestattet, ebenso Zusendung von Werbung oder ähnlichem) ----------------------------------------------------------- Mit freundlichen Grüßen, S. Schicktanz ----------------------------------------------------------- ------------------------------------------------------------------------------ Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d _______________________________________________ mseide-msegui-talk mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
