You are currently viewing the BOOK: Expert One-on-One Visual Basic 2005 Database Programming section of the Wrox p2p Programmer to Programmer discussion community. This is a community of more than 40,000 computer programmers including Wrox book authors and readers. As a guest, you can read any forum posting. By joining our free Wrox p2p community you can post your own programming questions and respond to other programmers’ questions. Registered users also don't have to see the ads that are displayed to guests. Registration is fast, simple and absolutely free so please, join today!
Join today and post to win prizes! Post more to increase your chances of being Wrox’s top poster of the month.
My question is a generic question related to architecture.
I am new to .NET. I am learning database programming using VB.NET 2005 from this book ("Expert One-on-One Visual Basic 2005 Database Programming") and have noticed the ample examples using bound controls.
My Question:
Should front-ends have bound controls at all? Say, you have SQL server as a back-end with your database and you want to build a front-end. Will you build your application with bound controls or is it better to build your application with unbound controls (that is, do not bound your controls to base tables at all). Instead have a one "I/O" class where all interaction with the back-end is done. That class serves your different data entry forms and your reports.
The intention is to be able to change the back-end schema as required without affecting the front-end (or vice versa).
Bound Vs Unbound controls
Linear Mode
