I quickly learned access if NOT the DB to use for web applications. My
guess here is that you were testing your application and it bombed
somewhere in the middle, you tried it again and got this error right?
Because when your app bombed the first time it left the connection open
and also "locked" the database. You will have to wait several minutes
for the lock to be auto cleared by the server.
Here are a few reasons to NOT use access;
1. The locking issues that you are experiencing
2. Its unstable and easy to corrupt
3. Access has limited concurrent connections. If you have too many
users accessing it you will get errors.
If you can get mysql (there are free versions available) I would use
that. Its way faster than access, you can have many more concurrent
connections, and it's VERY stable. You can get a web interface that
allows you to do almost everything you could do through access, like
view rows, edit rows, delete rows, add columns, etc. I was a die hard
MS Access fan for small web sites myself but when those small websites
started getting a little more popular I started having major database
problems. I also had random problems with locking and tables being
corrupt.
Since I've changed everything over to MYSQL, I have had no problems,
and my sites performance was immediately boosted. I know there are
probably a dozen people that are going to reply back stating otherwise
but the facts don't lie, and my experience with both db's proves MYSQL
is a much better choice.
Jeremy Reid
http://hgtit.com