Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Sometimes I need to develop a simple database application using MS Access Databases.
I`ve learned that I can manipulate data in my tables using direct SQL Commands or gather everything in a DataSet and update any changes that it tracks (insert, delete…).
But the question is: should my app make changes is my database tables using direct SQL commands or should I only use a DataSet, and why?
Thanks
The DataSets underneath use these commands anyway and you can edit/control them yourself (or leave it for the DataSet to build from your schema), but the DataSet also gives you other fast benefits such as designer support / change tracking / binding / filtering / sorting / etc
There is no “should” when working with a database, different tools will give you benefits and tradeoffs. For very small applications, either use the DataSet or do it manually. As soon as you step up from small, ditch the DataSet and look for other tools as DataSets will start to bite you with deficiencies that are annoying to code around.