Entity Framework 1.0 Error Unable to update the EntitySet XXXXXX because it has a DefiningQuery and no DeleteFunction element exists

Unable to update the EntitySet XXXX because it has a DefiningQuery and no <DeleteFunction> element exists in the <ModificationFunctionMapping> element to support the current operation" is one of the errors you will eventually run into with the ADO.NET Entity Framework 1.0.

This error is caused by the resulting SSDL that is generated when mapping a table with no primary key.  Adding a primary key causes an error with the association mapping, so that isn't a good option.  I saw some posts on modifying the generated SSDL, but did not want to mess with that every time I had to update the model.  There are different approaches to addressing the problem.  I have listed some of the links I referred to below. 

I am posting this because I didn't follow any of them.  I added an ADO.NET connection to my data access layer and simply went around the association maps found in the generated EDMX. 

I can do this because I am doing a proof of concept that includes EF, which means I am simply testing is value as a tool.  Right now EF is failing as a production worthy tool.  They have a lot to fix in the next release. 

Blogs and forums on the issue:
EF - Generate with No Table Key
MSDN Forum Post
CRUD operations in Siverlight using ADO.NET Data Service
Ado.Net Entity Framework Many to Many Relationships
DefiningQuery Element (EntityContainer SSDL)