about ADO.net

Why do programmers add lots of options to their software? Why have a WHILE DO loop when a FOR NEXT loop will do the same? And is the performance issue the same for both? Also, I am not inclined to share ADO techniques and methods on a forum that is intended for aiding in VB.Net programming. The topic of tiered data is way too broad to cover in the limited scope and nature of these forums. I would suggest that you find a library or buy a book on the subject.

Can you give me a full sample application using ado.net if this favor is not much to ask. thank you very much! jun mar

what is then the point of Microsoft to develop such technology that we cannot use it's full extent functionality and will affect the performance of the apllication. hope you can share your ideas with this... thanks....

As is the case with most programming, it really depends on the application. In general, I don't recommend keeping the entire database in memory (ie., in a dataset) unless doing otherwise would severely affect the performance of your application. As I outlined in my last reply, the tiered approach is considerd the best practice because it tends to balance resource needs with application needs.

thanks for your answer, i appreciate it much. But i guess your're missing my point when i say ideal. What i meant is that is it a good practice to maintain only one dataset for an entire database apllication. I know that a dataset set is an in-memory copy of the datasource; the tables, relationships, primary keys, indexes ect.

What so you mean by ideal? Do you mean a good practice? No, in actuality, your best practice is to have a tiered relationship. The tiers are like layers. At the bottom you have a core group of classes and structures that communicate with the database and provide for fundamental security. The next tier is your data tier which provide for the individual tables and datastructures. The business tier is where the structures are built and maintained. Without some example programming, this concept is difficult to comprehend, and if you want to know more, I suggest you read some books on the subject. In a nutshell, though, let's suppose that you need a record stored on an author table. Your application creates an object from a business class that represents the record that the application needs. The business class creates an object from the data tier. The data tier creates an object from the core. The core knows how to communicate with the database and acts as the mouthpiece (for lack of a better description) for the data tier. The data tier knows how to communicate with the core and set up the data structures needed for the business tier. The business tier reads the data structure and stores the information.