|
-
Jun 3rd, 2007, 03:59 PM
#1
Databinding
In VB6, bad, but what about in .Net -
should I be looking to bind the GUI and the database wherever possible?
or
should I just be running it off hardcoded queries?
or
does it not really make a monkey's if we're just talking about a single user on a local database?
-
Jun 4th, 2007, 06:22 AM
#2
Re: Databinding
If we are talking about a single user, with a local database, on one individual machine, then my vote would be whatever is easiest.
How important is security?
-
Jun 4th, 2007, 07:27 AM
#3
Re: Databinding
Databinding in .NET isn't the evil spawn of heck that it was in VB6... in fact it's better than ever. You can bind to just about any kind of object, including custom classes.
One of the things that made databinding so wrong in VB6 was the use of the DataControl, and it's inability to deal with certain situations.
A lot of the issues from binding in VB6 are now gone, and so much easier.
-tg
-
Jun 4th, 2007, 04:23 PM
#4
Re: Databinding
hmmm, thanks guys - good to know that Databinding isn't the devil incarnate anymore.
 Originally Posted by Hack
How important is security?
Security may be an issue - some data might be confidential
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
|