%USERPROFILE% in Command line

Attention Everyone.....This is a Terminal Server App! With everyone remoting
into the same Terminal Server, that is why I asked this question.


"Tom van Stiphout" wrote:

On Sat, 21 Feb 2009 12:35:46 -0700, John W. Vinson
wrote:

When I wrote "share the same one" I meant "on the same workstation".

-Tom.


On Fri, 20 Feb 2009 20:26:57 -0700, Tom van Stiphout
wrote:

On Fri, 20 Feb 2009 12:25:01 -0800, KPR
wrote:

Each user has their own copy of the FE on each workstation? You're
saying if 3 employees use a particular workstation from time to time,
you install 3 copies of the FE on that machine? Why can't they share
the same one? Typically there is nothing user-specific in a FE.

That's reasonable UNLESS the three users might be using the database
concurrently. Having a split database with a shared frontend gives you all the
disadvanatages of a shared database (bloat, corruption, contention, lockouts)
AND of a split database (network traffic, need to tune performance). I'm
afraid I'll have to disagree with you on this one, Tom!

On Sun, 22 Feb 2009 09:31:00 -0800, KPR wrote:

Attention Everyone.....This is a Terminal Server App! With everyone remoting
into the same Terminal Server, that is why I asked this question.


Two of my clients use this architecture (using Citrix rather than MTS but the
principle is the same).

Each user connects into their own private desktop, with their own private copy
of the frontend. The frontends all link to a shared backend (on a different
server, though in principle it could be on the same one); but I would NOT
recommend having multiple terminal server users sharing a single frontend (any
more than I'd let them share a single unsplit database).

The frontend must be on the server side, not on the client side - Access
doesn't "play nice" across the internet.
--

John W. Vinson [MVP]