R
Ronny Salomonsen
Hi,
I've got a Microsoft Access XP database with users running Access
2003. The customers are complaining about the record locking which
doesn't seem to work as it should. They are writing journal logs in a
form, then suddenly the data locks. The user would then have to wait
for anywhere from 2 to 60 minutes for it to open again. There are no
code that would make this happen.
We've set the database to use record level locking, and the form's
properties seems to be set to the same, so there shouldn't be a
problem there. The customers still seem to have a "page locking
problem". The strange thing is that sometimes it appears, and other
times it doesn't.
The database is split into two version, a MDB version for doing
administrative jobs, and a MDE version which the users use. The
customer which are having the problem has a Access 2003, but other
customers seems to have both Access XP and Access XP Runtime edition.
We are currently only seeing the problem at two customers, which has
5-15 users. The database is in JET format at the moment, but we've got
users running on SQL Server, but we haven't experienced any problems
there yet.
TEST___________________________________________
We did a little check on writing the contents directly into the table.
We create a new table called Eier in our data.mdb , then we log into
the MDB version of our frontned and start registering two new records.
We then open another session of the MDB file, add a record, then
switch back to one of the others and start editing without leaving the
record. We then use the first session and try to enter the record
being edited. There is a STOP-sign in the record selector, and it
doesn't show up on the other records. That's OK!
We then exit the two session and open two sessions of the MDE-version.
Both are using the same data.mdb , and we open the table Eier. We do
the exact same things as described above, but this time we've got a
page lock and none of the records can be edited.
So, my question is: why does the MDE and the MDB files act differently
when it comes to record locking? As it is at the moment, the customers
have a hard time doing their work since they can't register much data
before everything is locked.
I've got a Microsoft Access XP database with users running Access
2003. The customers are complaining about the record locking which
doesn't seem to work as it should. They are writing journal logs in a
form, then suddenly the data locks. The user would then have to wait
for anywhere from 2 to 60 minutes for it to open again. There are no
code that would make this happen.
We've set the database to use record level locking, and the form's
properties seems to be set to the same, so there shouldn't be a
problem there. The customers still seem to have a "page locking
problem". The strange thing is that sometimes it appears, and other
times it doesn't.
The database is split into two version, a MDB version for doing
administrative jobs, and a MDE version which the users use. The
customer which are having the problem has a Access 2003, but other
customers seems to have both Access XP and Access XP Runtime edition.
We are currently only seeing the problem at two customers, which has
5-15 users. The database is in JET format at the moment, but we've got
users running on SQL Server, but we haven't experienced any problems
there yet.
TEST___________________________________________
We did a little check on writing the contents directly into the table.
We create a new table called Eier in our data.mdb , then we log into
the MDB version of our frontned and start registering two new records.
We then open another session of the MDB file, add a record, then
switch back to one of the others and start editing without leaving the
record. We then use the first session and try to enter the record
being edited. There is a STOP-sign in the record selector, and it
doesn't show up on the other records. That's OK!
We then exit the two session and open two sessions of the MDE-version.
Both are using the same data.mdb , and we open the table Eier. We do
the exact same things as described above, but this time we've got a
page lock and none of the records can be edited.
So, my question is: why does the MDE and the MDB files act differently
when it comes to record locking? As it is at the moment, the customers
have a hard time doing their work since they can't register much data
before everything is locked.