Avoid the outdated tutorials. Right now youre writing Bad Code (TM) from an OO point of view because youre basically mashing all your code into one place. A button click event handler is NOT the place to be preparing an SQL statement and running it against a DB.
You'll also be amazed at how much hard work youre making for yourself, and tbh, it isnt even helpful or teaching you good things because (while i'm all for a "Make noobs program in Notepad so they appreciate visual studio" approach) all you end up doing is pick up baaad habits because everyone else does it too.
An arguemnt I usually use to sway people is:
Do you use the forms designer to make your forms and set your properties, or do you code all the layout stuff by hand? You bet you use the forms designer.. So a database access layer designer exists that generates great, modular, fast, working, safe code in seconds.. Why do you let it rest idle, and carry on writing your SQLs by hand, in a bad, slow, unsafe, poor-OO way?
Usually the answer is "because I don't know how to use it"
..and that's what DW2 is for..
In a little over the time it takes you to write the SQL to get your prefs value, i'll have a fully working code that prepares a statement, connects the db, retrieves the value, shuts everything down gracefully and returns me the value in type safe form.. I'll use it in one line too, making my code neater and more modular and reusable. What's to lose? Check it out.. No harm in using a wizard if it does a better job in seconds than most humans can do in a hour or more
|