Discuss "Database locked" in the Microsoft Access forum.

OK, I have a database that works great when used on 1 computer. Basically, a friend of mine has a dj show, and he wants an electronic request system. So, I came up with this database, which works great on one computer. I am attaching the database.

So, the problem is, the database is on the dj computer, and then there is another computer on the network that will be setup to for accepting requests. When I have the database running on one computer, when you try to open it on the other, it gives me a locked database error. Obviously the requests need to make it from one computer to the other. I'm pretty sure I didn't have it open exclusive. Any ideas...... I'm having a brain fart today, and I've not had much sleep.

Attached Files

invpos.zip (93.4 KB, 4 views)

Hey sben,

Have you tried using a split database? Give multiple copies of the "front end" to all the clients and then have one datastore on the network that all the front ends can connect to.

__________________
jmurrayhead
If you agree with me... click the icon!
If my post solved your problem, click the button in the lower right-hand corner of the post.

Join our Folding team: DeveloperBarn Folding

lol i agree with jmh,.. as i just posted the exact same in the "other" forum

__________________
If i helped you, make me famous by clicking the

ok, now that I split the db, it's saying on the other computer that it can't locate C:\thefolder\mydb.mdb. Basically, I copied the front end, and ran it from the location where the back end is. So on one computer, I have the database back end in C:\thefolder\mydb.mdb and the 2 front ends..... front1.mdb and front2.mdb. Computer 2 has that drive mapped, and when I run it, it says it cannot connect to c:\thefolder\mydb.mdb Do I need to copy front2.mdb to computer 2? Unmap the drive and use a folder shortcut? Is there a way to edit the connection strings for forms?

Are you on a client/server setup? I'm trying to understand how Computer A could possible reach Computer B via the path you are using. Do you have linked tables from the front end to the back end or are you doing everything via Jet? If using linked tables, you can modify the paths using the Linked Table Manager. Point those to the backend on the other computer.

Ok, so the solution was multi-pronged. First of all, I developed this on a server/client setup, so it worked where I developed it. When I installed the database on my friends dual computer network (no server/client), it had to be split. So the backend rested on Computer A, and I copied the front end onto Computer B (Not a link, the actual front end db). There was also a copy of the front end on computer A since both computers use the database. Then on computer B, I opened the front end, went to tables, right clicked on a table, and chose Linked Tables Manager. Then I selected each of the linked tables in the back end and also the box at the bottom that said "Always prompt for new location". I pointed it to the network share where the back end was, and the database worked as designed. I also did this for the front end on Computer A.