G
Guest
I've been following some tutorials and reading books and have a basic
grasp of the fundamental ADO.NET commands. But all the books I've read
use a database with only 1 table. My database has many, so:
1. I know there is 1 OleDbConnectino object variable per database
file, but is there one dataAdapter per table/query? (e.g. my tables:
tblCustomer, tblProducts, tblPrices etc etc, so should I have
dataAdapters such as these? daDataAdapterCustomer,
daDataAdapterProducts etc etc?
2. If there is 1 dataAdaptor per table, is there one Datatable per
DataAdaptor? e.g. (dtCustomer, dtProducts, dtPrices).
3. Am I right in thinking that in VB, the database connection
represents the database file, the dataAdapters are the intermediate
'link' to each table and the DataTables are the database tables held in
VB memory?
so I should modify the DataTables and when done save them using the
DataAdapter Update command to save them? (e.g.
daDataAdapterCustomer.Update(dtCustomer)
Sorry I know these are basic questions but I'd like to be 100% certain
before moving on to do more ADO.NET
grasp of the fundamental ADO.NET commands. But all the books I've read
use a database with only 1 table. My database has many, so:
1. I know there is 1 OleDbConnectino object variable per database
file, but is there one dataAdapter per table/query? (e.g. my tables:
tblCustomer, tblProducts, tblPrices etc etc, so should I have
dataAdapters such as these? daDataAdapterCustomer,
daDataAdapterProducts etc etc?
2. If there is 1 dataAdaptor per table, is there one Datatable per
DataAdaptor? e.g. (dtCustomer, dtProducts, dtPrices).
3. Am I right in thinking that in VB, the database connection
represents the database file, the dataAdapters are the intermediate
'link' to each table and the DataTables are the database tables held in
VB memory?
so I should modify the DataTables and when done save them using the
DataAdapter Update command to save them? (e.g.
daDataAdapterCustomer.Update(dtCustomer)
Sorry I know these are basic questions but I'd like to be 100% certain
before moving on to do more ADO.NET