This Recordset is not updateable.

[neo651]

I was updating several records on a table on the backend of a split database. Suddenly I went to update one of the records and I got an error sound and noticed at the bottom left it said "This Recordset is not updateable" and now I suddenly can't edit ANY of the records in this table. But I can still edit other tables in the database.

I've looked around for solutions and there are two things that seem to distinguish my problem from the similar situations I've found.

-This happened on a table, not a query.
-It happened abruptly while I was already editing table, not as soon as I opened it.

Anybody ever seen this before?

[ajetrumpet]

could someone else have the record opened too? if it's on the B/E and someone else has the record opened in a form on their F/E file, that will happen I'm sure.

[neo651]

No, I haven't gone live with the FE yet.

[NTC]

2 thoughts come to mind.

do a compact & repair

did you per chance move file to a nontrusted location

[neo651]

Even if I had moved the file, it locked me out after I'd opened it and after I'd already edited several records. One second I was editing and the next second it wouldn't let me.

[neo651]

The issue abruptly went away last week but came back again today.

-I can edit some tables in the database but not others, so it has nothing to do with where the file is located.

-The Front End of the database hasn't been distributed, so no one else is using it.

-I did a compact and repair. No change.

[boblarson]

Is the backend an Access backend or a SQL Server backend? Do you have primary keys set for each table?

[neo651]

It's an Access backend and all tables do have a primary key.

[boblarson]

It could be some corruption occuring. You might try importing everything into a new, blank Access database shell and see if it continues.

[neo651]

Corruption seems unlikely right now. I did exactly that 4 weeks ago because we had corruption already.

[boblarson]

Corruption seems unlikely right now. I did exactly that 4 weeks ago because we had corruption already.

Actually based on that statement I believe it is actually a greater chance that it is corruption than you might think. It sounds like you might have an issue which is causing corruption. Sometimes that can be a bad Network Interface Card or bad switch as well as just database related things. Try importing it into a new shell and see if it still has the problem.