Connecting Access in Multiple Locations 2

[romh]

Hi.
I have worked on an Access application at one location for a long time. I have a Windows 2000 Adv Server network and about 8 workstations. The database is split FE / BE. It works really well. Now I need to enable two other locations in the city to access the data in order to view inventory. What would be the best solution:
1) ASP through web site
2), Terminal Service
3), or some other method, maybe using Java. I am very experienced with Java.

I know that I will have to upgrade to SQL Server for improved performance, reliability and corruption issues.
I will probably have to use ASP in the future when the web site is completed. But for now, please tell me the advantages/ disadvantages of terminal service with Access 2000. I don;t know much about it.

Thankyou

 

[psemianonymous]

Terminal Server is, as I like to say, the Windows equivalent of telnet. You connect to the terminal server from anywhere, and run a virtual machine on the network. Everything you see will be from the point of view of the terminal server--it has its own desktop, network connections, etc. Your remote computer, located in the Bahamas or wherever else, receives screen updates to achieve the *appearance* of a remote connection.

What this means is that some features are not available via Terminal Server, like transferring files from your *remote* computer to the *Terminal Server* computer or elsewhere on the network. You also can't print, at least not on your remote computer.

What this also means is that, for all Access knows, your 10 remote users are all sitting in the server room, crouched over 10 different connections. This means that there is no performance hit for your remote OR local users, at least not moreso than adding local users. Basically, Terminal Server eliminates the word "remote" from "remote user". At a cost.


ASP is efficient, but involves a rewrite of all your code and forms into a web-based format. That's the downside--throw away your existing form code and rewrite it.


2. I don't think you need to upgrade to SQL server for performance reasons, though it won't hurt. 8 users can work with Access at the same time, so long as they're not doing massive simultaneous updates or batch reporting or generally overloading your system. Extreme lag time and/or database corruptions are signs that your database is overloaded.

On the other hand, moving to the server-based database will have many benefits, and from the sound of it, it's going to happen anyway, so go for it.

 

[romh]

Thanks for the advice. Extremely helpful. I would like to stay with the Access backend because so far, the performance is great. I use extensive VBA with unbound forms and try to compact regularly and decompile as well.
IF I use Terminal Server, would it be best to copy a front end on the terminal client. Is this even possible?
But from what you explained, everything runs froms the server and the client simply receives screen updates. So there would be no need for the front end on the client.
How often are the screen updates?

Thanks again

 

[psemianonymous]

If the bandwidth is good enough, it runs like any other Windows session, with a few hiccups every now and then. With a 56K modem connection, it processes new forms and user input within reasonable limits. Not fast, but worlds faster than most other interfaces. Just don't have any dancing baby animations running on the screen, and you'll be fine.

As for copying the front-end to the terminal server: yes, it does help. Terminal Server clients may not run the database without serious hiccups, but I hope your experience is better than mine was (see horror story at

http://dbforums.com/t842241.html

). Basically, you would copy the front-end to each user's profile on the terminal server itself (in my experience, M:\Personal). Do what you think is necessary and/or easiest for you; you can even set a different shortcut for the Terminal Server users and have them share a different front-end from your local users.

 

[Nassu]

Hi!

Just one comment ....
> You also can't print, at least not
> on your remote computer.

If we talking about Win2K Terminal server, then in Remote Desktop Connection settings (Local Resources tab) there are posiible connect local hard drives and printers to this session. I haven't tested local hard drives, but local printers (LPT-printers - not network printers) works well. With network printers You have to have a bit chemistry - map to LPT port and then add it to terminal session.

But check issue about Access instrallation in Terminal server environment - this is not trivial installation as in single-user machine. It must be installed through add/remove programs and as much as I remember, there were something additional to download (but I am not sure).

And another correction:
> copy a front end on the terminal client.
You can copy Your front-end to Terminal Server.

Hopefully helps...
Oleg

 

[romh]

Thanks Oleg.
I researched that you do have to reinstall Office 2000 with a few other settings in order for it to work with Terminal Server. I have one question though. When I tried installing Terminal Server on Windows 2000 Adv Server, it listed all the programs that I have in the hard disk and stated that I might have to reinstall all of them. That will be a pain if that's the case.
Furthermore, if I do copy the front end on the terminal client, I still don;t quite understand how that works. Will the client read all the forms and reports from the front end on his local computer, and then pull the back end from the terminal server? I need a little clarification on that.
Also, if I decide to go with the Advanced Terminal Server Client, how do the licenses work then. Do I just have to buy a server terminal license?

Thanks

 

[Nassu]

> I might have to reinstall all of them. That will be a pain if that's the case.
I suppose, that You have to reinstall only applications, which You want to run in Terminal server sessions. But I haven'n experience in this - I always have installed Terminal Server (Actually Win2K in TS mode) at first and then other applications.

> Furthermore, if I do copy the front end on the terminal client....
TS client is just a thin application, which transfers to You screen image of session (which runs on TS) and transfers back to TS Your mouse moves and keyboard clicks (like dummy terminals did if You know times 25 years ago). So Your FE must be installed in TS and BE must be installed also in TS or on some other file server in LAN (in which TS running). Each TS session opens separate instance of MSAccess FE on server (in own sandbox) and TS client have nothing installed except TS client itself (called Remote Desktop Connection). TS client only watching a screenshots from TS and works with keyboard and mouse.

> Also, if I decide to go with the Advanced Terminal Server Client, how do the licenses work then.
> Do I just have to buy a server terminal license?
Again as much as I know, if You use WinXP Professional as workstations, then TS on Win2k is free.On other platforms there are fees, but algorithm is quite sophisticated.

Oleg

 

[romh]

Thanks Oleg. I appreciate all your information.

 

[psemianonymous]

Sorry about the whole "terminal client" thing. What I meant to say is "client profile on the Terminal Server machine". Oops

 

[Hap007]

Just a quick comment.

I seem to have read that the latest Terminal server, which is just being released, allows the remote user to run a Terminal Server session on the TS box, but reports will print at the remote workstation.

I assume that it must be pretty involved to setup the needed printer drivers, (Since the trminal server would need to know what printer the remote user has installed) but if setup correctly, this is a powerful new feature in the latest version of Terminal Server.

Later,
Hap...

Access Developer

http://www.fcs-software.com/fcsaccessdev.html

-
Specializing in Access based Add-on Solutions for the Developer

 

[romh]

Sounds like a good feature Hap. Where did you read all that?

 

[Hap007]

Dear romh,

Follow this link:

http://www.microsoft.com/windowsserver2003/evaluation/overview/technologies/terminalserver.mspx

Then read about this feature:

Enhanced Remote Desktop Protocol (RDP)

Hope This Helps,
Hap...


Access Developer

http://www.fcs-software.com/fcsaccessdev.html

-
Specializing in Access based Add-on Solutions for the Developer