Re: To move or not to move to a Terminal Server

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance




The assumptions you are making are generally correct there's only a few
things I will add here:

Access 97 is not particularly good for releasing the processor and "idle
time" correctly. Access 97 is 10+ years old now and it is one of those
versions that was caught up in the transition between 16 bit computers and
32 bit computers. when running access 97 on a user's desktop, the fact that
it's a little worse and releasing the title processor time is not a big
deal, but when you're running multiple users on the same box such as
terminal services, and this can become a significant issue. I would suggest
that you use access 2003, or even the access 2003 run time.

The other issue that is significantly important is that even when you run
the system on terminal services, each individual user needs to get their own
copy of the individual front end. for some reason often when moving to
terminal services because everybody's theoretically to on the same computer,
this rule is changed, and access does not take well to what we call an
industry reentrant code.

so in terms of eliminating network problems, data corruptions, and a host of
a number of the issues, terminal services is gently of very good solution to
these type of problems and you'll usually get better performance as a bonus.

You likely can continue using access 97, but just remember it's going to run
the server processor a at little bit of a higher temperature range because
it does not "idle" the processor very well at all. This is also the case
when using access 97 on laptop, you find your legs getting very hot because
a97 doesn't always idle the processor.

There are other possible solutions to this scenario, such as moving the the
database to SQL server, but in terms of the least amount, the least amount
of reprogramming and least amount of changing your architecture, clearly
terminal services is you best choice especially since you're running an
already in you have it in house expertise.

using TS for all users means you'll never have to install or update
ms-access on the client side computers....

--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pleaseNOOSpamKallal@xxxxxxx


.



Relevant Pages

  • Re: Local Group Policy on Terminal Servers
    ... was up when I was applying a User Configuration policy to Computers. ... don't they have the Internet Security Zone settings on the Computer Config ... Your Terminal Services Security Website ... Security Zones under User Configuration - Windows Settings - IE ...
    (microsoft.public.windows.terminal_services)
  • Re: Want to lock out
    ... >I have done this - I created group called Servername Terminal Services ... >the users who log in to the terminal server while they are working use the ... >> Your Terminal Services Security Website ... >>>I have certain computers that I want to only access one of our 2 Terminal ...
    (microsoft.public.windows.terminal_services)
  • Re: Remote Desktop with GPO
    ... Allow users to connect remotely using terminal services. ... You can use this setting to configure Terminal Services remote access for the target computers. ... If the status is set to Disabled, the target computers maintain current connections, but will not accept any new incoming connections. ... >I have set up a GPO linked to an OU to "Allow administrators to connect ...
    (microsoft.public.windows.group_policy)
  • XP Clients using W2K Terminal Services - Strange Printer Issue
    ... I am running W2K Terminal Services and have several users that were connecting from home using W98 and W2K computers using the Remote Desktop connection. ... They bought new computers with either XP home or professional and now their printers will not redirect like they used to. ...
    (microsoft.public.win2000.termserv.clients)
  • Terminal Users Cant Copy and Paste
    ... I have users logged in via terminal services. ... have copied a large amount of text eventually the paste ... of a users clipboard, or perhaps another explanation? ... Chris ...
    (microsoft.public.windows.server.general)