Re: Which hardware upgrades are more important




David W. Fenton wrote:
Bri <not@xxxxxxxx> wrote in 98dvf.138293$2k.84712@pd7tw1no:">news:98dvf.138293$2k.84712@pd7tw1no:

TS only send the screen info down the line and this can be set to
send the bare minimum (min colours, no fancy see as you drag, etc)
so that the response is acceptable over a modem (56k or less
even). It doesn't take a lot of data moving to the FE to exceed
the screen data sent via TS.

On connections with more bandwidth than dialup, the responsiveness
is quite close to what a local desktop feels like.

Agreed. I use it via cable modem and the field via phone modem and TS can be tailored to both environments.


Security of the data isn't really the issue. AFAIK, Both TS and a
remote connection to SQL Server can be secured to similar levels.
. . .

But if your back end is Jet, the difference is gigantic -- there is
no way to serve up Jet data to an Access front end to remote
locations, unless you've got huge pipes for your WAN.

Agreed. Lyle was referring to remotely connecting to SQL Server, so I was continueing with that line.


One client, before being convinced to use TS, connected their remote office WAN via a broadband microwave link. The users still complained that the app was almost unusable (MDB BE at the time, currently SQL Server). We hooked up a demo of TS using the built-in admin remote desktop. They couldn't get that TS box ordered fast enough! :{)

. . . Integrity of the data is more important. ... and the
line goes down, then they could lose or corrupt the current
process.

That's really only relevant for a non-client/server app, no? That
is, with Jet?

Certainly more relevant with a Jet BE. With SQL Server (or other Client/server BEs I assume) there is still a window of time between the request and delivery where the data could be lost if the line goes down. The current process is potentially lost, but there isn't the same corruption issues that you have with Jet. With TS, their session continues to run, so when they reconnect its just like they had just like they had never left it.


Oh, and 'simple terminal' could be replaced with 'those older PCs/Laptops we can now keep around for a while longer'.

It means you don't have to worry about what they have on the other
end.


All other options for sharing data are much more complicated.

Agreed.

Oh, and I believe that you don't have to have Access installed to be
able to run Access on the TS. You just have to have cross-compatible
Office licenses. I definitely know that you don't have to have the
*same* version of Access installed. I don't have A2K3, but I can run
it on one of my clients' Terminal Servers.

The TS session runs completely on the server. The licencing of Office for the workstation is purely a legal issue not a technology issue.


--
Bri


.



Relevant Pages

  • Re: TS vs VPN
    ... Using TS, w/o VPN ... The remote client connects to your local TS via Remote Desktop. ... "Foo" accesses the SQL server, which is nearby in a protected part of the network. ...
    (microsoft.public.windows.terminal_services)
  • RE: Roll your own xtranet msde replication - Whats really required
    ... sql server functionality had been overlooked ... > where the remote clients cannot advertise their own services -- therefore ... > it help to split this into steps such that a client posts that it has data, ... >> are assimilated by the remote windows service, ...
    (microsoft.public.sqlserver.msde)
  • Re: Does anyone do SQL Server to Jet4 Merge Replication?
    ... I just found out that the JET merge-subscription capability has been ... dropped in SQL Server 2005. ... > We have a large legacy application built in MS Access (front-end client ... > replication to create a Jet subscriber database that could be used as the ...
    (microsoft.public.access.replication)
  • Re: Quick Question on SQL Server 2005 Express
    ... I have been away all week, but I can report that I did manage to connect to the "remote" version of SQL Server. ... I have now set up an Express version on our LOCAL server, and have linked a second Express version to this server via the network, as above for my client. ... We had discussed having our own licenced copy SQL Server 20052008, but with the cost etc, it was suggested that we use the licenced central server and a copy of Express to just hook up and do a bit of manipulation of our database. ...
    (microsoft.public.sqlserver.setup)
  • Re: Quick Question on SQL Server 2005 Express
    ... you can't attach a database in a remote machine in your network as Andrew has already mantioned. ... One database can be used only by one SQL Server instance and as far as I understand the database in question is already attached to a SQL Server instance. ... Why not installing only SQL Server Management Studio and connect to your remote instance and perform actions this way? ... The Client can live anywhere as long as it has TCP access to the server. ...
    (microsoft.public.sqlserver.setup)