G
Guest
I don't know if this is the forum where I should post this question but I'll
ask the question and hope for some advice.
I have developed an application in MS Access there is an increasing problem
of record locking issues creeping up. I have one table which two people add
records to on a daily basis (appr 200 records per day). This same database is
updated on a daily basis by up to 5 people. I can't say for sure what is
causing it but when both the data entry and the updates are happening on the
same table, some times, it causes a lock to happen such that no entries can
be created or updated in that table any more.
I realize my options are going to a SQL database as the back end but I am
looking to get your advice about all things that I can do to keep the
database in Access until I can migrate everything into SQL and make the
necessary programming changes. I do use Workspace coding yet once a month I
still get this problem. The problem sometimes doesn't get detected until we
notice that a save didn't work. I do use error trapping routines but they
don't seem to display for this kind of event.
To get my users to be able to continue recording records or updating
records, I have to get everyone out of the application or until I notice the
ldb file disappear for the offending file that contains the table with the
issue.
Any suggestions would be appreciated!
ask the question and hope for some advice.
I have developed an application in MS Access there is an increasing problem
of record locking issues creeping up. I have one table which two people add
records to on a daily basis (appr 200 records per day). This same database is
updated on a daily basis by up to 5 people. I can't say for sure what is
causing it but when both the data entry and the updates are happening on the
same table, some times, it causes a lock to happen such that no entries can
be created or updated in that table any more.
I realize my options are going to a SQL database as the back end but I am
looking to get your advice about all things that I can do to keep the
database in Access until I can migrate everything into SQL and make the
necessary programming changes. I do use Workspace coding yet once a month I
still get this problem. The problem sometimes doesn't get detected until we
notice that a save didn't work. I do use error trapping routines but they
don't seem to display for this kind of event.
To get my users to be able to continue recording records or updating
records, I have to get everyone out of the application or until I notice the
ldb file disappear for the offending file that contains the table with the
issue.
Any suggestions would be appreciated!