Hi,

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).

Which way would you recommend and why?

Thanks,
Richard