Access 2003 Slow on Terminal Services

[Jonathon]

Using Access 2003 on Windows 2003 Terminal Server. Both have service pack 1
installed.
When accessing a mdb over a network share, after more than one user
connects, it's slow recalculating the forms, etc.
I've done research, and found that this problem had been previously known
with other versions, and they had released patches. Does anyone know if
there is a patch for office 2003 to resolve this issue?

Here is the old issue I found, having the same problem.
http://www.tokeshi.com/modules.php?op=modload&name=News&file=article&sid=2133

 

[mrstwin2]

Jon,

This is a ongoing issue. I am in similar circumstances that you are.
Terminal server is not designed for knowledge users. You might want to read
the Microsoft white paper on Windows Server 2003 which contains alot of good
information. It also depends on your server configuration and hardware. I
had the memory bumped up just for MS Access/SQL Server and that seemed to
help some. You can only do so much with the software till you bump up
against the hardware limits. Plus Terminal Server will naturally be a bit
slower since you are not logged into that machine. Its all dependant if you
are on the same network or if you are a remote user. Wish I could give you
more information, but been looking myself and this is what I have found so
far.

 

[Jonathon]

Darn. Too bad. Not a server hardware performance issue.
I've checked both servers, the terminal server is a 4 processor server with
2 gb ram, and the database server has 750mb ish of ram, and 2 ghz. Neither
computer's resources are maxed out....
I was just following the trails of older versions of access.

Thanks for the reply.

 

[Rick Brandt]

Darn. Too bad. Not a server hardware performance issue.
I've checked both servers, the terminal server is a 4 processor
server with 2 gb ram, and the database server has 750mb ish of ram,
and 2 ghz. Neither computer's resources are maxed out....
I was just following the trails of older versions of access.

We have around 100 users hitting a two server farm with Windows 2003 running
several published apps (most of them Access) and have no perfromance
problems. Of course we are running Access apps that are installed ON the
terminal servers. Are your apps on the terminal server or elsewhere on the
LAN?

 

[asawyer]

I have a question about installing my app on a terminal server.
Since my app is split into FE and BE, I know the BE of course resides on the
main server, but does ONE copy of the FE reside on the TS server and all the
users use the same copy of it?? or do you have each user run it's own copy
of the FE by doing something special.

Thanks,
Alan Sawyer

 

[Mel Woolsey]

I have a question about installing my app on a terminal server.
Since my app is split into FE and BE, I know the BE of course resides on
the
main server, but does ONE copy of the FE reside on the TS server and all
the
users use the same copy of it?? or do you have each user run it's own copy
of the FE by doing something special.

Thanks,
Alan Sawyer

Alan,

Here is the way I have done it:

I put my frontend and any non-user-specific files in the C:\Program Files\My
"Application Name" file.

My application expects to get any user specific data from the user's My
Documents\My "Application Name" folder. So any user-specific files I put
there.

In the user's Desktop folder I put a shortcut to the frontend.

If you set up your Terminal Services Default user this way, every time you
create a new Terminal Services user, it will copy this information to the
new user.

Regards,
Mel Woolsey

 

[Mel Woolsey]

Oops! I misspoke. I tried putting my frontend in C:\Program Files, but
that didn't work. I ended up putting it in each user space in My
Documents\My "Application Name"; and I put the backend in a share file on
the domain server.

Regards,
Mel