In the DataAdapter Class section... I assume the "FROM HR.EMPLOYEES" is a table in the database. I'm not familiar with this type of notation. Two lines down: objDataAdapter.Fill(objDataSet, "Employees") I would have expected both of these tables to appear the same. In other words, I would have expected:
FROM EMPLOYEES or FROM Employees.

I looked for the database that this references but could not find it. There is no chapter 2 folder in the Wrox download and Chapter 1 doesn't have a figure with a table named HR.EMPLOYEES. I'm mostly familiar with DAO and Access. Maybe this is a SQL Server notation?

Thanks

HR.EMPLOYEES is the Employees table in the Oracle database that belongs to the HR user. This type of notation is used in both Oracle and SQL Server whereby the table name is prefixed with the owner of the object.

When filling a DataSet with data, objDataAdapter.Fill(objDataSet, "Employees"), we specify a name for the DataTable of Employees. A DataSet can contain multiple DataTable objects and this just helps us to refer to a DataTable by name instead of the index number.

I hope this helps clear up the confusion you had.

Thearon

Thanks Thearon,

I don't understand what it means to "belong" to HR user but that's okay. I understand that the string HR.EMPLOYEES would be replaced with the table name in my Access database. It took me a while to catch on that I could choose a different table name for the DataSet.

I prefer your book over the others I have because you offer information on OLE DB connections.

Thanks for responding on the forum!

Tom

Tom,

Let's say you had a user login created in either Oracle or SQL Server and your login had been granted the authority to create database objects (e.g. tables, stored procedures, views). When you create those tables, in this case the Employees table, the table will be prefixed with your login (e.g. Tom.Employees). You are effectlvely the owner of the table and it belongs to you. No one else can access that table unless they are granted permission.

Let me know if this needs further explaination.

Thearon

Thanks,

Now I understand! I've always created an Access database for a particular stand-alone application and never expanded my thinking to the notion of individual owners of tables until now.

Thanks for the responses!

Tom