database - Do you create classes to handle "entities" for data driven apps? -
I am a newbie and when I am roaming with creating a database application, I always make my form and all the codes and Put the binding on there
Now that I have developed a bit, then we say that I sold the wickets to customers and kept sales information in a database. If I was writing a program to access the database, would not I like to create such a class and 'widget' class to work with those institutions?
What is the proper approach to programming database applications if I'm making a mistake?
Yes
You want to see programming.
Basically, you only allow front end (presentation layer) access to your class library (business level). Your class library then reaches the database.
This gives you less tight solutions, and allows for a more satisfying code. Also allow you to rewrite the code in your foreground to allow changes in your DAB, as long as the interface of the business layer does not change,
as far as The compulsion is, if you are using the Visual Studio Windows Form (2005) then you should be able to use us so that you can use it to force your controls. If you are using ASP.NET, then your control should be tied in the list of objects without problems.
For ASP.NET, it may be worth seeing that I have not used myself, but there are many samples on the web.
Comments
Post a Comment