Yeah, as Richard mentioned you've probably got a naming conflict. Since it builds a class based on the table name when you add it a second time you get an error ...

So in my LINQ code, rather than using an explicit Join to attach the Customer to the Orders table, I can query the Orders collection and retrieve the Customer information through the Orders navigation ...