[AccessD] Access 2007 on a network

Charlotte,

<<I'm getting reports of people not able to log in
from elsehwere in our network. >>

 Login to Citrix or the app?

 Really there's nothing unique about Citrix over a normal LAN setup with
Access in the sense of the usual Access setup.

 Normal wisdom is to always give each user a copy of the front end as you
know.  Under Citrix, that's a bit different because everyone is sharing the
same C drive, so it takes a little bit of effort, but outside of that, it's
a straight Access setup.

  You can share the same FE between all users, but that's no different then
doing the same thing in a usual LAN setup.  In regards to the BE, a Citrix
setup can be even more robust as often the BE can sit on the Citrix server,
which means the local LAN is not involved at all.  That's not the case with
the usual setup of Access where the clients are reaching across the LAN to
access the BE.   If the BE is not on the Citrix server, then it's no
different then what you'd usually work with.

 Of course you do have to make sure a Citrix server has adequate resources
for the number of users it supports, but that's outside of Access and
something you'd check anyway Access or no.

<<All of use basically run off of
citrix drives unless we specifically save stuff to C:  Our "desktop" in on
a personal enterprise drive, so having them copy it there might not make
any difference;>>

  For any remote user, you want to make sure everything stays on the Citrix
server or you will have problems.  If a remote user installs the app to
their local C drive, then your running Access over a WAN.  If their in the
office and on the same LAN as the backend, then it doesn't make much
difference if they run through Citrix or their station (it would be a bit
faster going through their station though unless the BE sits on the Citrix
server).

<< and anyway, I'd have to make sure they all got the latest
build every day!  >>

  That's no different then a normal Access setup and can be accomplished
easily with a simple batch file.  Under Citrix however, each user needs a
drive mapping that is unique to them.  Normally a login script is setup
like:

  NET USE M: \\<Citrix Server>\Users\%username%\myApp\  


  This makes the mapping unique to each user and then within the app,
everything you do is with the "M" drive.   The only other wrinkle with
Citrix is references.  If you have any external DLL's or Active-X
components, users will still be sharing the same file unless you set the
reference with the "M" drive letter.   Not quite the normal situation, but
often overlooked when using Citrix and it can cause problems.

Jim.

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Charlotte Foust
Sent: Wednesday, August 22, 2012 09:45 PM
To: Access Developers discussion and problem
Subject: [AccessD] Access 2007 on a network

I've got a beta deployed on a citrix network.  Shared drive with enterprise
and I own the folder.  I'm getting reports of people not able to log in
from elsehwere in our network.  And I'm seeing corruption as a result of
their efforts. I use an mdb in 2002-2003 format.  I just want them to be
able to explore the thing, and I can't duplicate the issues from my machine
going into the same shared folder and just running it.  IT doesn't support
Access and wouldn't know how to start.  All of use basically run off of
citrix drives unless we specifically save stuff to C:  Our "desktop" in on
a personal enterprise drive, so having them copy it there might not make
any difference; and anyway, I'd have to make sure they all got the latest
build every day!  I'm not about to build an elaborate front end updater for
something that will evolve away from Access as some point, especially when
they still have nailed down all their requirements.

Any suggestions (keep it clean, please.  I'm a Buddhist)

Charlotte
-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com