Re: Access on VPN -- seeking solutions

evancater@xxxxxxxxx wrote in
news:517a8aa6-774a-4519-a4c5-792af1532911@xxxxxxxxxxxxxxxxxxxxxxxxxxx
m:

1. Do you know of a good written how-to source on the subject of
terminal services, preferably with a focus on using Access this
way? I need detailed instructions for an absolute TS beginner.

There's really not much to it. The most complicated part of it is
the licensing. With A2K7 you have to use the Enterprise version of
Windows Server and the Enterprise version of Access.

The only other issue is that many people think you can share a front
end on Terminal Server, but really, there's no difference between
running on TS and running on individual workstations -- ever user
has to have an individual front end.

2. When using this method, is the front-end usually accessed via
RDP or is it possible/preferable to have a front-end on each local
machine with tables linked to a backend that is in a central
location accessed remotely?

You get no benefit from doing it with the front end on the local
machines, and that just doesn't work over a VPN (except in very
carefully designed apps). The whole point of TS is that you're not
pulling anything across the wire except the video data. This makes
it very efficient and snappy.

3. Are there multi-user conflict issues using this method? Or does
it work just like a standard LAN based Access application, where
the data can be viewed and updated by multiple users at once? I
would guess the MDW file would be placed in the same location as
the backend?

The back end is the only MDB that will have multi-user issues, and
it's no different from having a shared back end on a server.

4. Does this method make it difficult for Access to automate other
programs like Outlook, Excel and Word?

That can be an issue, as automating those apps greatly increases the
RAM and CPU usage. Outlook has some gotchas working under terminal
server, if I'm remembering correctly, but I've never used Office
2007, so maybe the problems are different now.

I honestly don't believe in automating Outlook, in any event, but
frequently automate Word and Excel. But I've never done either
running on Terminal Server.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
.

Relevant Pages

  • Re: Automatically login to Outlook and a specific profile on a server?
    ... Outlook is not suitable for running on a server or automating as a service. ... A better solution would be to use CDO for Windows to send the message via a particular SMTP account. ...
    (microsoft.public.outlook.interop)
  • Re: Single user issue; best troubleshooting
    ... COULD be cause by that intermediate 'network access' server ... you do know there is significant logging in Outlook ... form of Integrated Authentication and so all of the OUTLOOK ...
    (microsoft.public.windows.server.active_directory)
  • Re: How to allow POP3 SSL connections w ISA 2004
    ... the Outlook group as well. ... Firewall Client configuration for ISA Server 2004. ...
    (microsoft.public.windows.server.sbs)
  • RE: login and email problems
    ... To the Outlook issue, ... Run "ipconfig /registerdns" command to register the DNS server. ... Ensure that you have an Outlook profile configured for the server ... profile is not associated with a Microsoft Exchange Server e-mail account. ...
    (microsoft.public.windows.server.sbs)
  • Re: RPC over HTTP
    ... We have already set up Outlook Web Access and purchase a SSL Certificate ... I have used the "outlook.exe /rpcdiag" to see if it uses the HTTP ... firewall through to the exchange server. ...
    (microsoft.public.windows.server.sbs)