[Accessd] FE/BE on server vs FE on workstation/BE on server?

Gustav Brock gustav at cactus.dk
Sat Apr 26 09:28:22 CDT 2003


Hi Drew

First, the FE doesn't have to be in the same network location as the
BE.

We use it quite a lot as we have dozens of customized apps running at
clients. Copies of these apps and their test data are kept on a local
file server in clients' directories with access for the support
people. In this way these can open the exact app that any client uses
from whatever workstation. If a revised version is delivered to a
client, a fresh copy is placed on the file server as well. It would be
an impossible job to have these copied to each and every workstation.

The added network traffic is negligible.

About the modification of a live database we just don't do that
whether it should be possible or not.

/gustav


> So tell me, other then the only obvious advantage I can think of, what
> earthly advantage is there in having a FE in the same network location as a
> BE?  The only advantage I can think of is that it allows for slightly easier
> modification of the FE, since a new copy can be put into place, without
> having to worry about the data in the BE.  However that really isn't an
> issue with 97, because 97 allows for modification of practically anything,
> as long as it's not in use (not the whole database).

> Drew

> -----Original Message-----
> From: Gustav Brock [mailto:gustav at cactus.dk]
> Sent: Thursday, April 24, 2003 3:38 AM
> To: accessd at databaseadvisors.com
> Subject: Re: [Accessd] FE/BE on server vs FE on workstation/BE on
> server?


> Hi Drew

>> eh?

> eh?? You're normally not that dense - or have you again being working
> all night ... what I mean is, of course, that putting the FE on the
> server has nothing to do with not splitting the database. If you take
> your precautions and the FE is nice and doesn't write to itself it can
> be perfectly safe to run it this way. 

> /gustav


>>> Putting the FE on the server is just like not splitting the FE to begin
>>> with.  That's about it, in a nutshell.

>> Ahh ... if so it doesn't fit in that nutshell.



More information about the AccessD mailing list