16-Nov-2005, 14:51 PM
|
 | Guest | | | | | | | | |
| Re: how open db read-only and exclusive?
thanks, just what I needed to understand
"John Vinson" wrote:
> On Tue, 15 Nov 2005 14:16:08 -0800, Liz James
> wrote:
>
> >A2003, split database on a network
> >how can the database be opened read-only using a shortcut? Does this mean
> >that read-only users can not update any data for sure?
>
> You can use the /ro switch in the shortcut to open the database read
> only; and read only means read only - the user will not be able to
> modify anything IN THAT DATABASE.
>
> However, there is no data stored in the frontend - the data is in the
Reference:: Sikh Philosophy Network http://www.sikhphilosophy.net/information-technology/7481-how-open-db-read-only-exclusive.html
> backend; they'll be able to use the (static, unchanged) frontend
> database to update the backend tables. See below.
Reference:: Sikh Philosophy Network http://www.sikhphilosophy.net/showthread.php?t=7481
>
> >I am having difficulty understanding the meaning of opening a db
> >exclusively. If db has both fe and be set to open exclusively -- I thought
> >(naively) this meant only one person could open their fe and use it to make
> >changes to data at any given time. Have tested and this is not the case.
> >Could you please explain. How is opening exclusively different from opening
> >in shared mode? In which circumstances should you choose to set the options
> >to open exclusively or shared?
>
> There are two .mdb files in play here: the frontend (one copy of which
> is presumably on each user's computer) and the backend. Opening the
> frontend exclusively means that nobody else can open THAT PARTICULAR
> FRONTEND. It does NOT affect how many different frontends can be
> linked to a given backend.
>
> Access is multiuser by default; especially when you're using a split
> database, there is generally no reason to require users to queue up to
> open the database exclusively. One user can be updating one record in
> a table, while a different user is updating a different record, or
> adding new records. Do you really NEED to have the backend (normally
> created so that it CAN be shared) unshared?
>
> John W. Vinson[MVP]
>  |