Once we have it in the bucket, we can use the data independent of the connection or adapter.
It is also good in that it is directly tied to the dataset itself.
So if we modify the dataset, the listbox automatically changes as well.
The disadvantage is that it can get a bit tricky to update the dataset itself unless you have a good picture of how that dataset is setup.
Keep in mind that this would be altering the dataset data, not the database.
So grab a drink, kick off your shoes and lets play with some snippets here on the Programming Underground!
So how do we get this stupid name column out of our table “Employees” of the access database and into a control? One is to connect to the database, another thing is to query the database for the info and lastly we put that info into our source control… Connecting to the database is pretty straight forward and really starts out with picking the right connection object from the System. Since Access can be “accessed” through the OLEDB setup we can use the Ole Db Connection class for that. This is nothing but a string that tells the class where to find the database, what driver (or DSN) to use, any username and passwords to login to the database, and any security features we will need to implement for our access.
The Data Adapter will use our connection (a well???
) and pump info into our Data Set which will be our bucket.
Like if we wanted to make sure that each name is properly capitalized we could do that before adding it to the list Box1. The last method here for selecting data is using a command object and fetching what is called a “Reader”.
This method is especially common because the command object is very flexible and good not only for select queries, but for updates, inserts and delete queries as well. We will use it again to show you a simple update in a second.
The first example will be to use a Data Adapter class and its fill method to load it into a Data Set.