Shared Database

[Guest]

We are using Access 2003 and have a shared database on our workgroup Server
2003 network.
Five computers could share the database when all the computers were in the
same building on the same network switch. We recently moved one computer
(Rec1) to a remote location that accesses our network via a VPN router. Now
computer Rec1 can only open the database if all other computers are off.
Once Rec1 opens the DB, Users 8 & 16 can open the DB but Users 6 & 10 can't
open it. When Rec1 is off, all other users have access to the DB.

The basic setup for Access on each of the computers with this DB is:
Default Record Locking - No Locks
Open databases using record level locking
Default open mode - Shared
All users have read/write permission for the database

I read one post that warned against sharing a DB on a WAN but gave no reason.

Any comments?

Paddler

 

[IRS Intern]

MDB is a crappy database, of course you can't run it on a real network
move to SQL Server, kid

 

[Guest]

Read/Write for the database isn't good enough. All users of the database must
have at least read, write, and modify privileges to the folder holding the
database file. Not just the database .mdb file, but the entire folder.

 

[Guest]

Read/Write for the database isn't good enough. All users of the database must
have at least read, write, and modify privileges to the folder holding the
database file. Not just the database .mdb file, but the entire folder.

I checked all the sharing and security provisions on the folder for the DB
and each of the potential DB users has the right to modify the DB.

Paddler

 

[John W. Vinson]

I checked all the sharing and security provisions on the folder for the DB
and each of the potential DB users has the right to modify the DB.

As Jerry says, *that is not enough*.

Users must also have the ability to create and delete files in the folder.
Access will create a .LDB locking file when the database is opened, and delete
that file when it is closed.

You may want to consider storing the data in SQL server and using ODBC to link
to it, if this is too big a security hole for your comfort!

John W. Vinson [MVP]

 

[IRS Intern]

John

why the hell would someone use ODBC?

Is ODBC _EVER_ going to be supported on x64?

OLE DB won the war, you're a ****ing retard if you're using linked
tables for any reason



Access Data Projects uber alles

 

[admin]

We are using Access 2003 and have a shared database on our workgroup Server
2003 network.
Five computers could share the database when all the computers were in the
same building on the same network switch. We recently moved one computer
(Rec1) to a remote location that accesses our network via a VPN router. Now
computer Rec1 can only open the database if all other computers are off.
Once Rec1 opens the DB, Users 8 & 16 can open the DB but Users 6 & 10 can't
open it. When Rec1 is off, all other users have access to the DB.

The basic setup for Access on each of the computers with this DB is:
Default Record Locking - No Locks
Open databases using record level locking
Default open mode - Shared
All users have read/write permission for the database

I read one post that warned against sharing a DB on a WAN but gave no reason.

Any comments?

Paddler

Try this....

Create a standard access database.
Import each of your tables from the primary mdb file into this new
mdb.
Remove the tables from your existing mdb and link the tables to the
new mdb using a UNC path (\\computername\sharename\path).
Give each user a copy of the mdb with linked tables (aka the original
file).