Set Up Terminal Services (Access 2000 and Windows 2000 Server)

Topic

New Reply

Can anyone either provide a simple list of the processes required
or point me at a good piece of text that goes through the basic steps
required to get an access database running on Terminal Services.

I have never done this before.
I have not even set up terminal services so it needs to be nice and simple
to start with.

i.e. What has to be done in what sequence on both Server and Client.

Once I have wrapped ny head round that, I’ll move on to any
more technical stuff.

Thanks in advance

Reply | Quote

Replies

What exactly are you trying to acheieve? You say you want to ‘get an access database running on Terminal Services’. If the Windows Server in question has Access installed then you can just do exactly what you would do on your local machine. Once logged into Terminal Services, just act exactly as if the desktop shown is the desktop of your local machine. Open the Access database and do your work.

Terminal Services allows users to concurrently log into a windows machine from remote machines with the resultant user interfaces being displayed on the remote machines, nothing else.

Application like Access are designed for user interaction and I fail to see the benefit of having it installed on a Windows Server rather than a local machine. A server is supposed to be used for running services and not user applications.

Reply | Quote

OK, let’s re-phrase the question.
I was requesting information on how to go about setting up terminal services.
If we were all on a local LAN I OBVIOUSLY would just use the database with a FE and BE
running local Access on the FE and just linking to the data.

BUT………………………………………………………………………………………
We have an access database that runs just dandy like that.
However, it needs to be remotely accessed across a remote dial in connection
or broadband, (it depends on who is connecting)
Terminal services seems to be the way to go.
The Server is running on 2000 (no chance of the extra cash for 2003), this is the real world.
I have never set up terminal services before, and I was hoping for a kick start in the right direction.

Thanks

Reply | Quote

Following up on my reply, we still split the database (the back-end might be either Access or SQL Server for example), and each person runs their own copy of the FE, even though it’s on the server, so we can deploy changes without kicking everyone out. As well, it minimized corruption problems and recovery when it does happen. Don’t however hold your breath on performance on dial-up. We find it works reasonably well when you have a 512KB download link to the server, but even then you may see occasional sluggishness in typing. At dial-up speeds it gets pretty bad.

Reply | Quote

Thanks again.

I think most will be using a 512 or higher connection speed.

Reply | Quote

Thanks again.

I think most will be using a 512 or higher connection speed.

Reply | Quote

Following up on my reply, we still split the database (the back-end might be either Access or SQL Server for example), and each person runs their own copy of the FE, even though it’s on the server, so we can deploy changes without kicking everyone out. As well, it minimized corruption problems and recovery when it does happen. Don’t however hold your breath on performance on dial-up. We find it works reasonably well when you have a 512KB download link to the server, but even then you may see occasional sluggishness in typing. At dial-up speeds it gets pretty bad.

Reply | Quote

OK, let’s re-phrase the question.
I was requesting information on how to go about setting up terminal services.
If we were all on a local LAN I OBVIOUSLY would just use the database with a FE and BE
running local Access on the FE and just linking to the data.

BUT………………………………………………………………………………………
We have an access database that runs just dandy like that.
However, it needs to be remotely accessed across a remote dial in connection
or broadband, (it depends on who is connecting)
Terminal services seems to be the way to go.
The Server is running on 2000 (no chance of the extra cash for 2003), this is the real world.
I have never set up terminal services before, and I was hoping for a kick start in the right direction.

Thanks

Reply | Quote

Terminal Services is a built-in feature of 2000 Server, but must be installed and configured. If you are planning on running it on a LAN however, there is no real benefit (unless you have very old and slow workstations). Where it really is of value is when you need to work on an Access database accross a WAN or the Internet. A quick Google search turned up http://windows.about.com/cs/terminalservices/%5B/url%5D as a starting point for 2000 Server. I should add that 2003 Server does a bit nicer job and is a bit more responsive. As ralphad points out, you do need to have Access installed on the server. We’ve used this approach pretty successfully, doing development and support to clients thousands of miles away.

Reply | Quote

Where it really is of value is when you need to work on an Access database accross a WAN or the Internet.

Yep, that’s the one.

I have gone to the web site suggested, and I am working my way through it now.

Thanks

Reply | Quote

Where it really is of value is when you need to work on an Access database accross a WAN or the Internet.

Yep, that’s the one.

I have gone to the web site suggested, and I am working my way through it now.

Thanks

Reply | Quote

Hi Wendell
Is there a more current tutorial you can point me at?

Reply | Quote