Thanks
Why Is It Evil For Some To Use Data Bound Controls?
Hot Topic
- Disappearing Binding Navigator Control Icons
- C Question
- What now? - x86
- where to get MicrosoftR Visual BasicR 2005 Express Edition: Build a Program Now!the registration benefits from
- long interval between StreamReader/StreamWriter processes
- Screenshot
- ListView Control
- Backing up installation on CD
- Installation Problem C# Express and SQL-Server Express
- Problems with SQL Express Beta
VS Express Editions
- listbox
- Command object
- Visual Studo C# 2005 Express Edition 8.0.50727.42 one bug?
- FindWindow API in VB2005 Express..??
- Failed to start monitoring changes
- what is System.IO.Port of ver 2.0 in Ver 1.1?
- character string functions in C++
- Include an Access database in VB express project
- Network Files
- How to Specify Form Location when Maximized
Why Is It Evil For Some To Use Data Bound Controls?
Kype
I wouldn't consider them "evil" in .NET.
Back in the pre .NET versions of Visual Basic most experienced developers frowned upon there use primarily because they were designed to create "quick and dirty" database applications. In addition there were several problems with these type of controls. First they were somewhat inflexible in that it was rather difficult to incorporate custom behavior. Second, you often had to work around idiosyncratic behavior to get them to do what you wanted. Third, they often didn't support the exact the functionality you needed which often required that you write DAO, RDO and ADO code anyway.
The data binding features in .NET are much improved, most of which is simply a byproduct of the improved architecture. However, I would still plan on writing some code in order get the functionality you need.
LeafBug_2k2