|
-
Sep 28th, 2007, 10:09 AM
#1
Thread Starter
New Member
Bound or Unbound? That is the question.
I'm a long time vb programmer and am moving our vb6 apps to vs2005 (finally). It has always been considered "bad practice" to use bound controls, especially on larger applications with a clear two or three tier architecture. All our front ends call backend routines that return datasets or arrays which are then loaded into grids, etc. Changes are then recorded and loaded back to the database via backend routines. Fully unbound processing.
Question is this; does anything change in .NET? Are there any compelling reasons to reconsider that strategy? I'm new to .NET and trying to get a feel for "best practices".
Thanks
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|