Update A Single Field in a Form Based on a Query

[erosenberger]

STUPID QUESTION ALERT!!!!!!!!!!

I am using Access 2000. I have a Form based on a Query that combines 2 db's. The reason why I did this is 2-fold, 1) so that 2 OLE files can be accessed from the different db's, and B) so that the end-user can go directly to a single record using a parameters pop-up. I have created a simple button to update a field within one of the db's - 'Me.Signature = "Mary"', however, because I have used a query, I cannot update the field because the "recordset is not updateable."

I am trying to avoid having to create an unbound form, as I'm sure most of you are aware of the programming nightmares that are involved.

Is there a simple solution to allow me to update the single field "Signature" in the db that I am just missing?

Thank you in advance for your help.

 

[erosenberger]

Worked like a charm. Thank you

 

[susor]

Similar Problem

I have the same problem except I'm joining FOUR tables. All have primary keys but I am getting the "Recordset is not updatable" message when I try and update. Is there another reason besides the lack of primary keys that would cause this?

Scott

 

[erosenberger]

If you are trying to update the tables utilizing a form bound to a query, you need to alter the recordset type.

To do so, go into design view, bring up the properties window for the form, and change the "Recordset Type" from Dynaset to Dynaset (Inconsistent Update).

 

[susor]

In my case, its one table with three 1-to-many's, plus one of the children has a 1-to-many with one of the other children. Don't ask. I didn't design it. There are also a couple of other things in the query such as a min function (looking for the earliest record of a grouping) and a calculation on a time field (looking for records 20 minutes old or older).

I set up a simple 1-to-many query and the updates worked fine. but with this "monster query" I get the good old "Recordet not updatable" message. I got around it by installing update buttons with separate update queries but that's not a great solution from a user perspective.

Scott