[AccessD] OT (Slightly) Using Windows Server with Access Database

Tom:

We have a client who has WinXP on workstations for the FE, Win2003 Server
for the BE, and is using AXP, on a 100 Mb ethernet. I just converted them
from A97 to AXP late last fall, so both Accesses (? Access's ?) will work,
and worked well.  There are about 30 workstations, all running Windows XP,
and the Client Application is on those, connected to the BE which is on a
Win2003 Server.  Normal operations have about 21 concurrent users, 15
which are the data input users (heavy), and the rest are view stations for
the most part.  They also have one Scanning station for imaging going to
the same server from one of the 15 workstations (uses different software
for that) but have had no visible delays/hangups/file locking issues.

There are a couple of things I have them do for administrative purposes
which may or may not be common, but seem to work really well for us and
them.  Each workstation has it's own copy of the FE.  It is uploaded fresh
from the server each morning on startup.  The related mdw file (this is a
fully secured database, using Access's built in security, users,
permissions, etc.) is also copied to each workstation fresh each morning. 
They have one Terminal Services server for outside users which is updated
by schedule each morning as well, since it's not restarted every day.  The
main purpose of this for network traffic, which is reduced by having each
computer have it's own copy of everything, but, in addition, I can
distribute any program updates/changes easily by just changing the source
file on the server.  However, I can distribute a clunker just as easily if
I'm not careful...which makes my phone light up like a Christmas tree...

Changing passwords, etc., is not quite as convenient, but that's not a
common thing with this client.

Overall, my comment is that using Win2003 Server on the BE with WinXP on
the client FE with either A97, or XP (or 2003) is very solid.  And fast. 
Even with 30 concurrent users.  I'm not sure about the 'dumb' terminal
idea reducing anything, and you may be in for a lot more work and expense
trying to set that up rather than using what your already have.

Our experiences with Win2003 Server a split Access 97, XP, or 2003
database have been very favorable.  If you are having issues with delays,
record locking, or BE corruptio