Many data types do not map easily to a database, and do not map to common form controls. Shoehorning data into a UI that it doesn't fit is an obviously bad idea.
But I disagree that data-bound controls necessarily means requiring the user to bend their view to the database rahter than vice versa. Choose your UI, and then choose your implementation. If you work that way, then when you use data-bound controls, you wind up having to work extra-hard to design the database tables to fit the UI.
Furthermore I'd say that whenever you have an impedance mismatch between how the database is organized and the user interface, you get problems. Those problems vary from limitations in performance to repeated bugs. This may or may not be seen as important enough to try to fix the impedance mismatch, but it is something to be aware of.
Cheers,
Ben