Runtime Error 2105 (1 Viewer)

agh81

New member
Local time
Today, 13:20
Joined
Dec 5, 2018
Messages
2
Hi, in an Access 2003 database all users can use it except one. When they open the database they get an error - Runtime Error 2105.
The debug goes to a line - DoCmd.GoToRecord , , a_NewRec
Any idea what would be causing this error for just one user?
 

theDBguy

I’m here to help
Staff member
Local time
Today, 06:20
Joined
Oct 29, 2018
Messages
21,357
Hi,

Are you restricting which users can add records? If not, then check if the user has write permission to the BE folder.
 

WayneRyan

AWF VIP
Local time
Today, 13:20
Joined
Nov 19, 2002
Messages
7,122
Shouldn’t it be acNewRec ?

Wayne
 

The_Doc_Man

Immoderate Moderator
Staff member
Local time
Today, 08:20
Joined
Feb 28, 2001
Messages
26,998
If this code won't create (and then travel to) a new record, it is usually something to do with folder permissions or form settings or opening issues.

I'm going to rule out form issues a priori because you stated that only one user is getting this problem. If this issue had to do with forms and everyone is running a front-end copy of the same form, then it is not form settings. Unless you are running forms smart enough to respond based on user role,

That leaves folder issues. With respect to the folder in which your database is being touched, does the problem user have Windows MODIFY permissions on that folder? And READ permissions on all folders above the one that holds your database? More direct and to the point, how are you assigning permissions on the folder? Per each username? OR did someone make a group identifier for you?
 

agh81

New member
Local time
Today, 13:20
Joined
Dec 5, 2018
Messages
2
Thanks for your help. It turned out the user was in 2 permission groups for the BE folder. 1 giving modify access and 1 read only, the read only group had deny write permissions set. Once removed from the read only group the user could open the database without error.
 

theDBguy

I’m here to help
Staff member
Local time
Today, 06:20
Joined
Oct 29, 2018
Messages
21,357
Hi. Glad to hear you got it sorted out. Good luck with your project.
 

The_Doc_Man

Immoderate Moderator
Staff member
Local time
Today, 08:20
Joined
Feb 28, 2001
Messages
26,998
Yep, got to watch out for those groups - they are additive BOTH ways. The "Grant" entries are added and the "Deny" entries are added separately. But a "Deny" overrides a "Grant" so that READ group blocked the MODIFY group. It's similar to that old rule about "attaboy" and "awshit." (One "awshit" cancels a thousand "attaboy"s.)

In general, when putting permissions on a group, you want to make the group either GRANT permission or say nothing at all. You rarely want to use a DENY unless it is very specific. And in a multi-user shared setting, a DENY will reach up to bite you. The way Windows permissions work, you can put a GRANT on something or not. You can put a DENY on something or not. And you can leave something unmarked either way. If the security arbitrary code reaches an unmarked permission slot, the default is to DENY but the thing is, THAT kind of denial can be overridden by a GRANT. An explicit DENY is more of a problem.
 

Users who are viewing this thread

Top Bottom