Runtime error 2105

C

C Tate

An organisation which uses our database has started getting the following
error message: 'Run-time error 2105. You can't go to the specified record'.
There is also a message at the bottom of the screen which states that the
record-set is not updateable. The database is on a network and the other
computers are all able to enter information ok. I have completely
re-installed the front end on the affected machine but this does not solve
the problem. I did think the problem might lie with the backend. Perhaps it
is locked in some way? However, this does not really explain why the other
computers can still view and enter information on the database as normal.
Can anybody suggest anything to overcome the problem? The user does not have
a backup of the data so I cannot try replacing that!
 
W

Wayne Morgan

If the users are all using copies of the same front-end, are all using the
same logon account/permissions on the back-end, and you've tried replacing
the bad front-end with a known working copy, then I would guess that there
is a problem with the network share permissions for that user or the "patch
level" is different on that computer. Check the current versions of the
Office patches/service packs, Jet service pack, and MDAC service pack.

For Office, go to http://officeupdate.microsoft.com and let it scan the
computer for needed updates. Compare the results with another computer. For
Jet, find the Msjet40.dll file in the %windir%\system32 folder (Win2k/WinXP)
or the %windir%\system folder (Win98/ME), right click it and choose
Properties. Go to the Version tab and compare the version with another
computer. For MDAC, you can check the MDAC level using

http://www.microsoft.com/downloads/...f6-4a21-4b43-bf53-14332ef092c9&displaylang=en

You can find updates for MDAC and Jet at http://windowsupdate.microsoft.com
or http://msdn.microsoft.com/data/downloads/updates/default.aspx
 
C

C Tate

I have now tried all the update things you suggested so i am thinking it
must be a permissions problem. What is the best way to ensure everybody is
using the same permissions on the backend?
 
W

Wayne Morgan

It depends on which permissions. If it is the database permissions, the best
way is to have them all use the same user name and password in the Access
User Security setup. If the problem is network/NTFS permissions, then the
best way is to have all of the users in a "group" and assign the share/NTFS
permissions to the group.

The Access User Security doesn't use the Windows logon as the basis for its
user name and password, they are separate, so you can assign the same user
name and password to users with common functions and access needs and not
affect their Windows logon. However, doing this can make it more difficult
(but not terribly) to track who is making changes, if you need to do that.
If you do, then give each user their own user name for the database and, as
in the network setup, place the users in a group and assign the permissions
to the group, not the individual users.
 
Top