Error 3113 field not updatable

[Nigel]

I have a system that imports an Excel sheet and either appends records to a
table or updates data in a table. These two processes use in-code SQL for an
append or update query. The system has been working fine for several years

Recently a couple of users (on unrelated networks) have received error 3113
[Field not updatable] when running the stage that uses the update query (the
append works fine).

The only way I can simulate the error is by making the MDB that holds the
target table read-only before running the update process. This generates the
same error but the append process fails too which does not happen for the
users.

The only common feature between the two users appears to be that both have
had 'computer support' staff rebuild their PCs and re-install
Windows/Office. In addition, both append and update processes do appear to
work on another PC suggesting that something specific to the user's PC or
rights has changed.

Any ideas what might be happening ? I suspect network rights or MS-Access
time-out / refresh settings but still can't resolve problem. Is the error a
red herring?

Nigel

 

[Allen Browne]

To test the idea of permissions, log in as a local administrator, and see if
the error is reproducable.

Another thing to check is the version of msaccess.exe and msjet40.dll on
these two computers. Are they the same as on the machines that do not give
the problem?

Name AutoCorrect can cause problems where Access gets confused about field
names. Details:
http://members.iinet.net.au/~allenbrowne/bug-03.html

There is also a strange error that occurs if the action query contains
multiple tables, but you would experience that issue the other way around
(i.e. with the Append query, not the Update query). It relates default
values being set in the table that is not being updated.

 

[Nigel]

Allen

Thanks for the suggestions. I'll see if they can try the log-in idea. It's
not auto-correct though - I should have said in first post that they're
running Acc97, so no autocorrect nor msjet40.dll.

Nigel

To test the idea of permissions, log in as a local administrator, and see if
the error is reproducable.

Another thing to check is the version of msaccess.exe and msjet40.dll on
these two computers. Are they the same as on the machines that do not give
the problem?

Name AutoCorrect can cause problems where Access gets confused about field
names. Details:
http://members.iinet.net.au/~allenbrowne/bug-03.html

There is also a strange error that occurs if the action query contains
multiple tables, but you would experience that issue the other way around
(i.e. with the Append query, not the Update query). It relates default
values being set in the table that is not being updated.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.

Reply to group, rather than allenbrowne at mvps dot org.

I have a system that imports an Excel sheet and either appends records to a
table or updates data in a table. These two processes use in-code SQL for
an
append or update query. The system has been working fine for several years

Recently a couple of users (on unrelated networks) have received error
3113
[Field not updatable] when running the stage that uses the update query
(the
append works fine).

The only way I can simulate the error is by making the MDB that holds the
target table read-only before running the update process. This generates
the
same error but the append process fails too which does not happen for the
users.

The only common feature between the two users appears to be that both have
had 'computer support' staff rebuild their PCs and re-install
Windows/Office. In addition, both append and update processes do appear to
work on another PC suggesting that something specific to the user's PC or
rights has changed.

Any ideas what might be happening ? I suspect network rights or MS-Access
time-out / refresh settings but still can't resolve problem. Is the error
a
red herring?

Nigel