how to create shared database

[Guest]

how do i create a shared database where more than one user can update
information

 

[Keith Willcocks]

how do i create a shared database where more than one user can update
information

Put the tables in one database and the application in another. Each user
gets a copy of the application database which is then linked to the tables
in the tables database (File/Get External Data/Link Tables).

 

[Guest]

many thanks keith but what is an application? as you can guess i'm new to this

 

[Guest]

thanks keith but what are applications? as you can guess i'm new tro this

 

[Douglas J. Steele]

It's possible that Keith had something else in mind, but typically what's
meant by an Access "application" are the queries, forms, reports, macros and
modules. The database in which those objects exist is typically referred to
as the "front-end", while the tables and relationships are in what's
referred to as the "back-end".

Only the back-end is placed on the server: each user has his/her own copy of
the front-end, ideally on his/her hard drive.

You may find these references useful:
http://www.granite.ab.ca/access/splitapp/index.htm
http://www.members.shaw.ca/AlbertKallal/Articles/split/index.htm

 

[Guest]

With the greatest of respect, it sounds as though you would have a tough time
trying to create an Access database if you're not familiar with the basics
such as the meaning of an "application".
I've been there, having started with Access only a year or two ago, and
despite having spent many years fiddling around with a variety of PC
software, I have to tell you that there was quite a learning curve.
I strongly recommend that you get yourself a book that will explain the
basics - something like Access for Dummies - I have never used the Dummies
series before but I found this one invaluable.
Little Black Crow

 

[Guest]

many thanks for this. i have actually created quite a large database & was
seeing if there was an easy way to share it.

 

[germaine.oliver]

I think many people can create an Access database even if they aren't
familiar with that particular usage of the term "application". Most
people think of an application as something like Word or Excel.
Thinking of something created in Access as an "application" is non-
intuitive for most users. That is one of the beatiful things about
Access... it is accessible to people at all knowledge levels. I had
some pretty decent Access skills before I ran into the first use of
the term "application" for a front end (which, btw, is what I think
most people use when referring to Access apps.) But despite the
handicap of lack of terms, some of my Access dbs were pretty useful
and functional.

But I agree completely: the "Dummies" series is WONDERFUL. I used the
Access Programming for Dummies book (in Access 98... wow, I'm old)
frequently. Even for those with a good knowledge base and the
capability of making good databases can get good information from
these books.. and for newbies, I can imagine they're awesome....

 

[Keith Willcocks]

If it is all in one database. Create a second empty one, import your
tables into it from the original, then delete the tables in the original and
use "File/Get external data/Link tables" to connect to the new database.

 

[germaine.oliver]

Isn't this what the database splitter does?

If it is all in one database. Create a second empty one, import your
tables into it from the original, then delete the tables in the original and
use "File/Get external data/Link tables" to connect to the new database.
--
Keith Willcocks
(If you can't laugh at life, it ain't worth living!)







- Show quoted text -

 

[Keith Willcocks]

Quite possibly, I have never used it as I always set mine up in two
databases to start with.