View Single Post
  #1 (permalink)  
Old January 3rd, 2007, 08:42 AM
Richard_AU Richard_AU is offline
Registered User
Join Date: Jan 2007
Location: Melbourne, Victoria, Australia.
Posts: 3
Thanks: 0
Thanked 0 Times in 0 Posts
Default bound Vs unbound controls on front ends


My question is a generic question.
I am new to .NET. For now I am learning VB.NET 2005 from wrox books with ample examples of bound controls using ADO.NET.
But, 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 one "I/O" class where all interaction with the back-end is done. That class serves your different data entry forms and your reports.

Which way would you recommend and why?

Reply With Quote