Am Mittwoch, den 16.05.2007, 10:09 +0200 schrieb Frank Schönheit - Sun Microsystems Germany: > Mathias' suggestion gets the most points :). The BoundField property of > the control model refers to the database field which the control is > bound to. Modifying this one is, speaking strictly, the only proper > solution.
In general I can second your opinion, but there *are* cases where using the control is "a good thing": Especially when using BASIC there is no way of converting datatyes using an API service (at lest one I know, please tell me if so!) so you'd have to convert each value to the type the bound fields wants to see. In BASIC this blows up code by factor three (I know for sure, because I have made some read- and write-back-macros for database data in calc sheets :P ). If one uses the control/view in this scenario the only types to detect are Date-, Time- and FormattedField bindings, all the rest is text. The conversion and format checking is done behind the scenes. I used this approach for copying a record in a form as template for e new one (excliding the primary key field). Maybe I could name some more use cases if I'd think about it ... ;) If I would, my conclusion would be to RFE a converting service to and from control types and database field types ... Marc --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
