In-house server to WAN and T1 environment

[Niranjan]

Hi
We have an Access 2000 database application in Windows 2000
enviroment. They will be moving to a new location but the servers will
be at the same old location that they currently are (They are moving
within the same city). The new environment will be WAN and T1 lines
with the same software operating on the same servers.
I am supporting this database (a relatively complex App of 13 MB and
backend database of about 10 MB. What should I be looking for as far
as performance is concerned. Will Bandwidth be an issue? If anyone has
experienced a scenario like this one or is currently operating in one
like this, please inform me of any issues I should be concerned about.

[Tony Toews]

nh****@hotmail.com (Niranjan) wrote:

We have an Access 2000 database application in Windows 2000
enviroment. They will be moving to a new location but the servers will
be at the same old location that they currently are (They are moving
within the same city). The new environment will be WAN and T1 lines
with the same software operating on the same servers.
I am supporting this database (a relatively complex App of 13 MB and
backend database of about 10 MB. What should I be looking for as far
as performance is concerned. Will Bandwidth be an issue?

Performance and stability will suck bigtime. Your options are replication, Terminal
Server/Citrix or SQL Server. Possibly MSDE dpeneding on the number of users.

Or put a new server at the new location. That'll likely be the cheapest option.
Note that a client was running 15 users on a Pentium 400 NT 4.0 server which was the
only server for about 50 office users. So you don't need the latest and greatest
here.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm