Re: using access on terminal server

Tech-Archive recommends: Fix windows errors by optimizing your registry


There's probably no simple answer, Roy. The key is probably to establish
just where the existing bottle-necks lie. The network is an obvious
candidate, but there are many other possibilities, including the design of
the application and database, the server hardware, and what other demands
are being placed on the network and the servers. If the app is very
carefully designed to retrieve the minimum data necessary across the
network, and the database is carefully designed, with appropriate use of
indexes, then I suppose placing the front-end on the clients might reduce
network traffic. On the other hand, if the app is not so carefully designed,
then it is entirely possible that placing the front-end on the clients might
increase network traffic. I doubt that anyone who isn't intimately familiar
with your environment can predict the result.

--
Brendan Reynolds
Access MVP

"Roy Goldhammer" <roy@xxxxxxxxxxx> wrote in message
news:ey4HiDFGHHA.2128@xxxxxxxxxxxxxxxxxxxxxxx
whell bob:

the back-end is sql server.

my question is: today 100 users are using terminal server and i'm thinking
about improve the system by placing the mdb on each client pc computer.

that is quite hard to do due to things i've explained before.
so all i need to know, is there advantage to place the mde on local pc
instead of using terminal server?

"bob" <rgalway@xxxxxxxxxxxxx> wrote in message
news:OoPppc$FHHA.1280@xxxxxxxxxxxxxxxxxxxxxxx
1. Access works best in a front-end (local PC), back-end (network PC)
mode. Less than 10 concurrent users.

2. With less than 10 users, my experience is that Terminal Services works
OK also.

3. Once past 10 users start to think about using SQL server on the
back-end. 255 is theoretical max but ~ 10 is a practical max.

Bob


"Roy Goldhammer" <roy@xxxxxxxxxxx> wrote in message
news:%23Uth075FHHA.3976@xxxxxxxxxxxxxxxxxxxxxxx
Hello there

I have business which has sotware written in access.

the mdb file is stored on the server and any user that runs the access
using terminal server on each computer.

there are at least 100 users. and the access is working very slow.

i'm thinking about option of moving to use the file as local on each
computer instead of terminal server. The network performance isn't good
on the business (10mbps) and the mdb is using some activeX components of
visual studio and ect...

can someone give me an advice, should i trasfare to work on local access
instead of terminal server?







.

Relevant Pages

  • RE: Opening from cache instead of network, while working online?
    ... is accessing the larger files over the network. ... i am looking at a way to teach them to use the Offline files ... Any setup that requires the file sync of a 50MB file is going to ... Microsoft MVP - Terminal Server ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: Terminal Server with 2 NICs
    ... could saturate your internal network. ... What is the bandwidth and latency of the connection these remote ... MCSE, CCEA, Microsoft MVP - Terminal Server ... TS is open for logon attempts from the Internet, ...
    (microsoft.public.windows.terminal_services)
  • Re: Access on VPN -- seeking solutions
    ... use it to create a network. ... than 16 people accessing through hamachi. ... use the terminal server to create users for each person that you ... grant thier access to functions and forms and information. ...
    (comp.databases.ms-access)
  • Re: Sharing printers on TS
    ... You can buy devices that will put a non-network printer on a network. ... Terminal Server via a VPN connection. ... When she logs into the Terminal Server she can ... security settings on the printer that they stay, ...
    (microsoft.public.windows.terminal_services)
  • SBS 2003 VPN issue through ISA
    ... We have a SBS 2003 premium box with a 2003 Terminal Server on the same ... The XP clients and the terminal server use a VPN for a third party ... The weird thing is that the XP clients work fine and nothing has changed on ... the network, except maybe some Windows updates that have been installed. ...
    (microsoft.public.windows.server.sbs)