Front-End on server or on workstation ?

I have seem in this list people saying to split the database and put the
back-end on the server and #a copy of the front-end to each one of the user's
stations#. Is that so?

I have my databases splitted and put both database on the server (but
separated), so I am sure everybody is using the same version of the
front-end. Is there a problem on this approach?

Thanks
Mauricio Silva

Mauricio Silva wrote:
I have seem in this list people saying to split the database and put
the back-end on the server and #a copy of the front-end to each one
of the user's stations#. Is that so?

I have my databases splitted and put both database on the server (but
separated), so I am sure everybody is using the same version of the
front-end. Is there a problem on this approach?

Thanks
Mauricio Silva


Multiple people in the same front end often leads to corruption problems in both
the front end file and the data file. There are numerous ways to automatically
distribute front ends to each user's PC to ensure that they are using the newest
version. Tony Toews has a free utility that does exactly this. On a good
network and with a front end that is not too large you can simply copy the file
from a master copy on the server every time it is used by having the user click
on a shortcut that runs a simple batch file.

--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com

I my environment I have:
- 7 back-end
- 8 front-end databases
(so far)

each one of the front-end uses data from more than one back-end (1 of them,
is connected to all back-ends). The front-ends are located in shared folders,
according to its purpose and users privileges. (Projects, Sales,
Management,...)

I still fail to see how the front-ends and the back-ends could became
corrupted, once nobody has privileges to open the design mode in my database.
Is there some paper or Microsoft report talking about this? (If I need to
change this, I need something to show to my boss).

Unfortunately, download something from the internet is out of question
(Company's policy) so, I'll have to find a easy way to deal with this.

Thanks for your comments

Mauricio Silva



"Rick Brandt" wrote:

Mauricio Silva wrote:
I have seem in this list people saying to split the database and put
the back-end on the server and #a copy of the front-end to each one
of the user's stations#. Is that so?

I have my databases splitted and put both database on the server (but
separated), so I am sure everybody is using the same version of the
front-end. Is there a problem on this approach?

Thanks
Mauricio Silva


Multiple people in the same front end often leads to corruption problems in both
the front end file and the data file. There are numerous ways to automatically
distribute front ends to each user's PC to ensure that they are using the newest
version. Tony Toews has a free utility that does exactly this. On a good
network and with a front end that is not too large you can simply copy the file
from a master copy on the server every time it is used by having the user click
on a shortcut that runs a simple batch file.

--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com

Mauricio Silva wrote:
I my environment I have:
- 7 back-end
- 8 front-end databases
(so far)

each one of the front-end uses data from more than one back-end (1 of
them, is connected to all back-ends). The front-ends are located in
shared folders, according to its purpose and users privileges.
(Projects, Sales, Management,...)

I still fail to see how the front-ends and the back-ends could became
corrupted, once nobody has privileges to open the design mode in my
database. Is there some paper or Microsoft report talking about this?
(If I need to change this, I need something to show to my boss).

The entire time you are in the front end Access is constantly pulling
objects from the file over the network to the local workstation and is also
periodically saving bits of information back to the file. This happens even
when no design changes are made and even in an MDE file. With multiple
peolple in the same file "stuff happens" while this is going on which oftne
leads ot corruption.

It's sensible to argue that it "shouldn't" be this way, but it is
nonetheless.

--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com