<shudder>
I am in the unfortunate position of supporting a bunch (about a dozen)
of Access97 databases created by the infamous "Bad Contractor".
She built all of her applications as unsplit and just put shortcuts on
all the user's workstation desktops. Over time I've been able to
split the ones with the heaviest user load into FE/BE.
I have a couple of ... "problem children" who never respond when I
announce a new version of the front end, so I can put it on their
computers, and insist on using the front end located on the network.
Because of the environment around here, I am unable to change this.
So, predictably (almost like clockwork), I have to repair corrupted
Access applications. In fact, I had to do it just yesterday. One of
the users *willfully* (though maybe not maliciously) bypassed my
hand-rolled security. Heh ... then proceeded to delete my security
measures and fuxored the application.
I love Access. It's my "go-to" tool for much of what I do but, if
it's not set up properly (check this out:
http://www.mvps.org/access/tencommandments.htm)
you WILL regret it.
My tuppence 'orth,
RD
On Wed, 29 Jul 2009 18:56:30 GMT, "JimBurke via AccessMonster.com"
<u49905@uwe> wrote:
>Why is this a bad idea? Just curious. Guess I'm showing my ignorance of how
>Access works - sorry for the bad advice! It seems that any app running on a
>server can potentially have many users.
>
>Dale_Fye wrote:
>>Bad idea Jim.
>>
>>It is NEVER a good idea to have multiple users using the same front end! Now,
>>if you mean give each user a copy of the front end on the server, and use
>>Terminal Server, then I'm in agreement.
>>
>>Dale
>>
>>>Is there a reason why each user needs a separate copy of the front end? It
>>>sounds like they're all using the same back end. If your back end is already
>>[quoted text clipped - 14 lines]
>>>>
>>>>Thanks,
>>