ecastillo090698
asked on
Error 3051 with Access 2000
I have a Vb application using access 2000 that worked well before using version 97. Now I am geyting this error: Run-time Error 3051, for the sixth user that conect to the net. The first five work well, but the sixth recieve this message error. I am using windows 2000 profression.
I'm using DAO 3.6 ... and the sentence that i use to open de database is "Opendatabase(base,false,f
Thx.
Eduardo Castillo A.
I'm using DAO 3.6 ... and the sentence that i use to open de database is "Opendatabase(base,false,f
Thx.
Eduardo Castillo A.
https://www.experts-exchange.com/questions/21079777/Run-time-Error-3051.html
usually this error is indicative of attempts to open a database exclusively that is already under the control of another user.
Permissions for the folder in which the database exist MUST be set to FULL Privileges. Read access is not sufficient
usually this error is indicative of attempts to open a database exclusively that is already under the control of another user.
Permissions for the folder in which the database exist MUST be set to FULL Privileges. Read access is not sufficient
ASKER
I have tried changing the users and computers, and it is not important that user is or if pc is, the sixth one always falls down for this error (3051).
The users enter to the Operative system with the only account, with sufficient permissions.
In the VB application the call to open the DB not mention user's name not password. The curious thing is that it falls down always in the sixth connection.
The users enter to the Operative system with the only account, with sufficient permissions.
In the VB application the call to open the DB not mention user's name not password. The curious thing is that it falls down always in the sixth connection.
Are you sure they have full access to the DIRECTORY and the FILE?
ASKER
Yes, because as I said previously, they enter with one only account ... and the five first ones in connecting can use allways the DB without problems.
Hmm, Access can deal with a max of 255 users (don't recommend that, but theoretically is't possible), thus the sixth can't be the problem.
Looks however that one user does get exclusive access rights. When someone would be updating the database this error will also occur, is your code somewhere updating forms, reports or modules?
Nic;o)
Looks however that one user does get exclusive access rights. When someone would be updating the database this error will also occur, is your code somewhere updating forms, reports or modules?
Nic;o)
ASKER
Well, they all have total rights (they all enter with the same account, if one can access, all should be able). Now the application falls in the sixth user in connecting to the DB, and in the function that tries to open the DB ... the other users are not updating in that moment.
I was thinking that has something that to see with Access's capacities 2000 of groups and own(proper) users to create ... but I not as(like) sending this additional information from VB DAO (Opendatabase).
I was thinking that has something that to see with Access's capacities 2000 of groups and own(proper) users to create ... but I not as(like) sending this additional information from VB DAO (Opendatabase).
Sounds like seat issue. Trying to remember OS which has five-seat limit. Using NT by chance?
ASKER
The server who has the DB is windows 2000, the stations that connect are XP ... it is strange ... but it is the situation...
W2k professional?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Nic;o)