sharing a database

C

christiekp

I'm sure the answer to this is somewhere but I don't have the time to
search.. sorry!

I created a database on a shared directory on the network and it's only
allowing one person in it at a time. What do I need to change to allow all
in at the same time. The database provides data but requires no input by the
other users.

thank you
 
R

Roger Carlson

First thing to check are the network permissions. Everyone who uses the
database MUST have CREATE rights as well as READ, WRITE, and EXECUTE.
(DELETE is nice too, but not strictly necessary.) The reason for this is
that if a user doesn't have Create rights, they can't create the LDB file.
If there is no LDB file, Access assumes the first user has opened it
Exclusively. Giving the correct permissions will resolve the issue.

--
--Roger Carlson
MS Access MVP
Access Database Samples: www.rogersaccesslibrary.com
Want answers to your Access questions in your Email?
Free subscription:
http://peach.ease.lsoft.com/scripts/wa.exe?SUBED1=ACCESS-L
 
C

christiekp

The rights you're referencing are in tools/security/users and groups
permissions? All rights are 'X'd'
 
G

Guillermo_Lopez

First thing to check are the network permissions.  Everyone who uses the
database MUST have CREATE rights as well as READ, WRITE, and EXECUTE.
(DELETE is nice too, but not strictly necessary.)  The reason for this is
that if a user doesn't have Create rights, they can't create the LDB file.
If there is no LDB file, Access assumes the first user has opened it
Exclusively.  Giving the correct permissions will resolve the issue.

--
--Roger Carlson
  MS Access MVP
  Access Database Samples:www.rogersaccesslibrary.com
  Want answers to your Access questions in your Email?
  Free subscription:
 http://peach.ease.lsoft.com/scripts/wa.exe?SUBED1=ACCESS-L








- Show quoted text -
Click to expand...

Christie,

The easiest way to do this is to have a Backend and a Front end. From
your explaination i assume everyone is running the same file in the
common drive. You'll have the same problem if you do the exact same
thing with an excel file.

The back end containes the database, with all the shared information.
No forms, no codes, no queries, just the tables.
The front end, has all the codes, forms, queries, macros, and modules.
And the only tables it has are those specific for the file, that do
not need to be shared. Then all the tables are linked from the Back
end in the shared drive while EACH user has their own Front End.

How to do this. Make a backup first. Create a new Database. Import
into your new database all the shared tables from the original. Then
open the original DB and delete all the tables that you have sent to
the new DB. Then link all the tables in the New DB. Make sure that the
New DB is already in the Shared drive so that the link works the same
on everybody. Then check that everything works, and finally send a
copy of the Old DB to everyone, and ask them to run that from thier
computers.

A couple of things to note. If you have a large amount of data, this
method might be slow. If your Shared drive is slow (say because it's
located in another state), this method will be utterly slow. This will
not improve performance but will allow multiple users to access the
data.

Other more eficient methods is to use a SQL server/ MySQL/Oracle/DB
whatever server with all your data as your backend. This will improve
performance expecially if you have 100+ people accessing the data at
around the same time.

- GL
 
A

aaron.kempf

SQL Server will improve reliability, performance, scalability-- just
with a single user.

SQL Server will keep your data _SECURE_.
Access cannot physically secure data in any way.

If you run your database in 'another state'- then you don't need to do
anything.. except move to SQL Server.

SQL Server supports these new-fangled things called 'networks' and
they work like a charm over all types of networks.
When Access does anything fishy-- these guys around here blame it on
the network.. or the design.. or the users.

The only reason that people use Access as a database-- is because
you've got some Senior Citizen on the payroll... That doesn't have the
mental capacity to learn a real database.

Move to SQL Server or just use Excel if you're a retard.

-Aaron
 
C

christiekp

Thank you to those that were helpful.

Aaron.. I think this was a bit harsh.
"Move to SQL Server or just use Excel if you're a retard."

Sometimes you do the best you can with what you have. I gave our users the
ability to get reports and query data without asking the finance department.
Our IT dept is a pay for service (wholly owned) company and frankly,
sometimes it's easier to operated in your dark ages than to give basic excel
reports.
 
J

John W. Vinson

I'm sure the answer to this is somewhere but I don't have the time to
search.. sorry!

I created a database on a shared directory on the network and it's only
allowing one person in it at a time. What do I need to change to allow all
in at the same time. The database provides data but requires no input by the
other users.

thank you
Click to expand...

Just be sure it isn't being opened exclusively, and make sure you're not
opening anything (forms, reports, etc.) in design view. See Tools...
Options... Advanced and uncheck Exclusive.

HOWEVER... for a shared application, you should *really* split it into a
backend containing just the tables, and a frontend containing everything else.
See http://www.granite.ab.ca/access/splitapp.htm for a thorough discussion.
 
G

Glint

Aaron,
Thank you for your very thoughtful and inspiring advice. Sorry if I am a bit
slow, but I still have not figured out why a smart guy like you has not
realized that Access has something for 'retards' like us, and that we like
it. Perhaps you can persuade Microsoft to eradicate Access instead.
 
A

aaron.kempf

They already did!!!

Now they're jamming sharePoint down your throats.. because you fools
were too stupid to use SQL Server.

Honestly-- anyone using Access as a database-- in the year 2008--
should be fired on the spot. There is no excuse.
SQL Server is bigger, better, faster, cheaper, more powerful.

SQL Server has _TOOLS_.
Access has _NONE_.

SQL Server has _INDEXES_.
Access doesnt' really.

SQL Server has _TONS_ of functionality that you have to 'write
yourself' if you want to use access.
Linked table? Auto Link?

Screw that-- move to SQL Server and you wouldn't need to deal with
anything like that.

The only reason that anyone would use Access as a database-- is
because they're too old to learn a real database.

Honestly.

Good Luck--

-Aaron
 
G

Guillermo_Lopez

They already did!!!

Now they're jamming sharePoint down your throats.. because you fools
were too stupid to use SQL Server.

Honestly-- anyone using Access as a database-- in the year 2008--
should be fired on the spot.  There is no excuse.
SQL Server is bigger, better, faster, cheaper, more powerful.

SQL Server has _TOOLS_.
Access has _NONE_.

SQL Server has _INDEXES_.
Access doesnt' really.

SQL Server has _TONS_ of functionality that you have to 'write
yourself' if you want to use access.
Linked table? Auto Link?

Screw that-- move to SQL Server and you wouldn't need to deal with
anything like that.

The only reason that anyone would use Access as a database-- is
because they're too old to learn a real database.

Honestly.

Good Luck--

-Aaron





- Show quoted text -
Click to expand...

I get it! You must be the lead developer for SQL Server. You had us
fooled there Aaron, didn't you!!
 
A

aaron.kempf

whatever punk.

SQL Server runs circles around Access MDB / ACCDB.

The only reason to use MDB / ACCDB is because you're too stupid to
learn the worlds most popular database.

SQL Server isn't any harder-- it's just that you kids have been
driving a stick for so long.. you're _SCARED_ to learn to drive an
automatic.

This automatic is cheaper, more reliable; more scalable.. easier to
drive and maintain.

There isnt' a single benefit to Access MDB / ACCDB.

Sorry

;)

-Aaron
 
Top