B
Boss
How can i share a database file over a network.
Kindly help.
Boss
Kindly help.
Boss
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
F
FredFred
Here's the KISS (Keep it Simple) answer . my favorite kind.
The mdb is just a file like any other file. Users need to have access on
their machine. Then they just open access and open the file or double click
on the file.
They can even make shortcuts to it although Microsoft keeps making those
not work well by impairments with defects that they call "security".
The mdb is just a file like any other file. Users need to have access on
their machine. Then they just open access and open the file or double click
on the file.
They can even make shortcuts to it although Microsoft keeps making those
not work well by impairments with defects that they call "security".
P
Pat Hartman
Start by moving the database to the network share you want to use. Then
split the database either manually or by using the splitter wizard. You can
leave the front end on the server but it is best to distribute a copy of the
front end to each user's local drive. This leaves you with the data in a
database on the LAN which can be shared by all and the "program" part of the
application located on each user's own computer. With the split setup, you
can replace the front end without worrying about disturbing existing data
and you minimize the potential for corruption because, the users are only
sharing data rather than a monolithic application. If any of this is Greek
to you, do some searching on splitting a database for more details of why it
is better.
split the database either manually or by using the splitter wizard. You can
leave the front end on the server but it is best to distribute a copy of the
front end to each user's local drive. This leaves you with the data in a
database on the LAN which can be shared by all and the "program" part of the
application located on each user's own computer. With the split setup, you
can replace the front end without worrying about disturbing existing data
and you minimize the potential for corruption because, the users are only
sharing data rather than a monolithic application. If any of this is Greek
to you, do some searching on splitting a database for more details of why it
is better.
D
Douglas J. Steele
While that might be the simplest approach, it's definitely not the best. The
application should be split into a front-end (containing the queries, forms,
reports, macros and modules), linked to a back-end (containing the tables
and relationships). Only the back-end should be on the server: each user
should have his/her own copy of the front-end, ideally on his/her hard
drive.
application should be split into a front-end (containing the queries, forms,
reports, macros and modules), linked to a back-end (containing the tables
and relationships). Only the back-end should be on the server: each user
should have his/her own copy of the front-end, ideally on his/her hard
drive.