The fact that the table doesn't have a primary key was a bad thing, but it *could* have told you that was the reason it wouldn't allow updates.
I'll note that a *real* database (like SQL Server) happily allows inserts, updates, and deletes to such a table. What's amazing is that the database *was* SQL Server, but Access *still* knew better than you what to do.
I've heard it said that it can take a database programmer a year to recover from Access poisoning. :D
(I'm happy that your problem was solved, though)
Custom Apps, Inc.