MS Access Multiuser - Shared Front End .mdb

Author

Shared Front End .mdb

Peter-d

2005-09-09, 8:25 pm

Hi everyone

I've got a FE/BE application that's been succesfully used for a couple of
years. When I took it over, it was setup as a replicated db. Being a bit
ignorant about replication (still am), I did not like it that way and changed
it bback s=to a simple front end /back end app where all the users access the
same front end mdb.

It's been working fine for a couple of years and the app has significantly
grown in complexity.

I see a lot of posts here that seem to imply each users having a copy of the
front end on their workstation and tools that allow making sure the local
file is current.

I'd like to hear what you think of having multiple users accessing the frend
end mdb on a network file share (currently same as the backend).

I've got 25 potential concurrent users (rarely more than 10 are actually on
at the same time) and i'm using A2000.

Thanks for your wisdom.

Larry Linson

2005-09-10, 3:24 am

"Peter-d" wrote

> . . .
> I see a lot of posts here that seem to
> imply each users having a copy of the
> front end on their workstation and
> tools that allow making sure the local
> file is current.

Actually, you see a lot of posts here that _definitively state_ that each
user should have his own copy of the front end on his own machine. And, you
see a lot of posts here that explain _why_: if you have multiple users
logged in to the same front end or monolithic database, you significantly
increase the chance of corruption.

> I'd like to hear what you think of
> having multiple users accessing the
> frend end mdb on a network file
> share (currently same as the backend).

I think it is unwise.

People have run without problems for years, but then make some minor,
apparently inconsequential change and are faced with frequent, and
inexplicable, issues of database corruption.

> I've got 25 potential concurrent users
> (rarely more than 10 are actually on
> at the same time) and i'm using A2000.

If you had only two users, my answer would be the same. However, it does
appear that the heavier the use, and the more users, the worse the problem
will be.

Larry Linson
Microsoft Access MVP

Alex Dybenko

2005-09-10, 3:24 am

Hi Peter,
shared frontend solution will work, but nobody would recommend using it,
bacause of possible corruption and higher network traffic. No clear why are
you asking about this, if you have concerns using local FE on each PC - then
let us know

--
Alex Dybenko (MVP)
http://alexdyb.blogspot.com
http://www.PointLtd.com

"Peter-d" <Peterd@discussions.microsoft.com> wrote in message
news:A945CE3C-38ED-42B7-86BA- BCA0E24E333C@microso
ft.com...
> Hi everyone
>
> I've got a FE/BE application that's been succesfully used for a couple of
> years. When I took it over, it was setup as a replicated db. Being a bit
> ignorant about replication (still am), I did not like it that way and
> changed
> it bback s=to a simple front end /back end app where all the users access
> the
> same front end mdb.
>
> It's been working fine for a couple of years and the app has significantly
> grown in complexity.
>
> I see a lot of posts here that seem to imply each users having a copy of
> the
> front end on their workstation and tools that allow making sure the local
> file is current.
>
> I'd like to hear what you think of having multiple users accessing the
> frend
> end mdb on a network file share (currently same as the backend).
>
> I've got 25 potential concurrent users (rarely more than 10 are actually
> on
> at the same time) and i'm using A2000.
>
> Thanks for your wisdom.

Sponsored Links