MS ACCESS DB cannot conenct multiple users

[jayztek]

must have posted wrong forum

so here it is

Ok so i setup ms access on a terminal server

all i want to do is allow multiple users to connect via term serv and see an existing ms access DB,

when i connect via rdp as administrator then try to view the db if it is already in USE by another term serv user i CAN DO THAT

but if TWO term serv users try to connect they get a locked already in use error

things i have done

in the db i made the db a shared db
in security i have made users the owner on all tables and such
in the properties of the folder holding the db i adjusted to give EVERYONE and all remote users all rights

anyone else have any ideas

this is not a complex db, it just stores info on a group of people and we all need to view it at once for reference?

 

[lameid]

When in a multi-user situation the standard advice is to use a split database and have each user have a copy of his own front-end.

You could try setting up each user with his own front-end on the terminal server.

But if you only need to view it, I suspect giving everyone File Permission of Read only to the folder and file may work to. The caveat here is that if anyone with read only permission has the file open, no one with Read/Write Acccess will be able to open the database and vice versa. If you are using a split database and have the backend in a folder where all users can change the file, this is less of a problem. In that scenario you could shedule a copy to overwrite the copy for terminal server with the source periodically to ensure updates.

I hope that helps.

 

[jayztek]

hi

so i tried to make a SPLIT db, and it created a "backend db" but when i had two remote users log in it said "file in use" so i dont think access is the way to go with this type of collaboration, im thinking of movbing it to ACT

but who knows let me know if you have any other ideas

 

[lameid]

Alas I don't have enough knowledge about Terminal Server to know that causes the exclusive lock.

I am assuming you have set the Access options to not open exclusively with the database open.

The only other possibility I can think of as a work around is a copy of the front end for each user... then they will not be using the same copy and it does not matter if the file is locked. This is of course a tedious solution but I think it will work.

You might have better luck with the Windows Server forum too... If you post there and get a response, please be sure to link the thread here.