Recordset Not Updateable

[GUIDO22]

Upgraded my aging database application from 2007 to Office 365 and most of the database appl. works fine - apart from this form which errors as shown...
Has anyone any ideas why only now this is 'making noises' after several years of running flawlessly.....?

(I have noticed that none of the relationships appear in the relationships window as they used to , suggesting they have not been migrated to the new DB file... could this be the problem...?)

Thanks in advance...

 

[Minty]

I would suspect that it's because you are opening a recordset on the same data as the form is based on, and you aren't specifying that the recordset should be a snapshot, so it is opening it as a dynaset.

Try adding
, dbOpenSnapShot
to the end of your Set rs line.

 

[CJ_London]

A couple of other points - as Access matures it becomes less tolerant of poorly defined code. You aught to be defining rs properly - dao.recordset and you are using reserved words in your field names (Description). Also that error could be because the recordsource your form is not updateable.

And your other error message is referring to Office12 (i.e. 2007), probably need updating to whatever version of office you are now on - look in tools>references to see the version

 

[GUIDO22]

Thanks all for your input... although I had changed the form Recordset type, I had overlooked the subform... having changed this to Dynaset (inconsistent updates) - all works as it did before....

 

[Pat Hartman]

Also, to efficiently refer to controls on the current form AND get intellisense, use:
Me.SomeControlName

rather than controls!somecontrolname

The additional difference is that you will get a compile error if the field doesn't exist just in case you didn't notice that intellisense didn't work. Using the controls! method, you wouldn't get an error until the line of code was excecated. You ALWAYS want to get errors at compile time rather than run time whenever possible. Run time errors just make you look dumb to the users.