OK, you guys won; I'm trying out SQL Server. I found a kink in how .NET 3.5 handles Entity association members, but hopefully my work-around will work in all cases. The kink is if you have an entity class with an association EntitySet, you have to give that member a value before using the InsertOnUpdate DataContext method. I'm also learning that assigning an association a value might bullox future queries. EntityRef's, on the other hand, don't require values. E-mail me at pelayorex@insightbb.com if you want me to post my code.
Ross