I am developing my first project using Typed datasets.

Here is the problem i cant get my head round.

I have got two datatables which are related to each other. i want to access the columns from both the tables( ie inner join). 

How can i do that such that i have datasets which are typed.

assume table1 and table2

select table1.*,table2.* from table1 inner join table2 on table1.matchedDataField=table2.matchedDataField

please mark as answer if this helps u.

you can not apply inner join directly on resut set (Typed DataSet).

There are few styles to acheive this

1. You can write filter conditions based on both & select the required records from it

2. If you use LINQ on DataSets, you can write down

3. If you use some ORM model to get data from Server like Linq-SQL or ADO.net Entity Framework you can acheive this very easily

follow this link

http://www.c-sharpcorner.com/UploadFile/rupadhyaya/TypedDataSets12032005021013AM/TypedDataSets.aspx

Okay, so if i cant get a typed dataset that contains the data from both tables. That makes it useless. And defeats the whole purpose of creating  typed dataset and sticking to tiered architecture.

Taking about Linq, i havent used it much but the problem i have with it is i dont want to learn lambda expression and all. Plus people have mentioned the lack of control on your sql in this approach.Generally not really fond of the concept of OR mappers

Doesnt that leave us with Data Access Block(enterprise library), the only problem i have with it is there should be a way to synchronise, (Buisness objects)classes with Database tables.

Hi Ahasan,

As suggested above, it's not supported by now to write JOIN queries in typed dataset directly. The normal way is to use stored procedure instead. That means, you could write a stored procedure with JOIN queries in database, and use it in typed dataset. A custom type will be auto-generated to store the results returned in stored procedure. Please take a look at this tutorial first:

http://www.asp.net/Learn/data-access/tutorial-68-vb.aspx

Thanks.