Re: Database Split and Linked Table
- From: "Chris Mills" <phad_nospam@xxxxxxxxxxxxxx>
- Date: Sun, 9 Jul 2006 13:49:19 +1200
It may be the best way to run a seperate copy of the FE on each individuals
computer but I have been running several DB's with both the FE & BE on the
main servers for a number of years without any major problems.
Interesting point. So did I on one smallish site "just for the hell of it" and
I had no major problems either. My thinking was "if I don't try it I don't
know!", also for a similar reason to Jeanette that the program was initially
changing quite often (in itself, a bad practise!<g>)
Nevertheless, there are very sound reasons for Doug's advice. All I can say is
that, certainly an FE can be run on a server, but it is "best" to run it on
each client PC. For example, it will run "faster" / in a given case however
it might very well be "fast enough" anyway. Though it's more likely that
developers want to do everything they can to improve speed, reliability, etc,
because those are often ("usually?")("nearly always?") major issues with
Access.
All of which just means, I agree it's "best" have separate FE's! Perhaps an
analogy might be, I s'pose my car might run for quite some considerable time
even if I don't give it the proper service! (I do, by the way) <forget
that-weird analogy>
Some procedures (such as situations which require temporary tables, an import
perhaps) will not work the same (or as easily or reliably) if everyone is
using the same FE.
It is NOT difficult (in my opinion) to keep separate FE's updated. Even before
Tony Toews' well-received updater (or anyway), I had version checking on
startup between FE and a version number held in the BE. That way, I could
force users to upgrade if their FE was "forgotten about", they restored from
an old backup, got hold of an older CD, whatever. All these things happen!
Besides, sometimes an upgrade to a product also includes changes to a BE,
making it incompatible with older FE's, and this is not too difficult to
handle with a reasonable scheme and separate FE's either. Sort it out once,
and you can use the same "proper" scheme for all subsequent programs you
write!
I can't really believe another comment of yours, Bob. I've installed software
on some reasonably large sites, and I tell THEM how my software installs not
vice versa. Separate FE's does not appear to me to be an issue which affects a
given corporations security policies or whatever, or in any case if their
policy conflicts with very sound Access advice. I am required to keep my
software running, and I can only do that if they take my advice (whatever it
may be <g>).
Chris
.
- References:
- RE: Database Split and Linked Table
- From: jeannette_rivera
- Re: Database Split and Linked Table
- From: Douglas J. Steele
- Re: Database Split and Linked Table
- From: Bob Hughes
- RE: Database Split and Linked Table
- Prev by Date: How To Open Access MDE on Citrix Server
- Next by Date: Re: Database Split and Linked Table
- Previous by thread: Re: Database Split and Linked Table
- Next by thread: Re: Database Split and Linked Table
- Index(es):
Relevant Pages
|