Emmanuel Katto from Dubai : Database Performance Issues on Terminal Server Running Access Runtime (1 Viewer)

[emmanuelkatto24]

Hi Team,

I'm Emmanuel Katto from Dubai, United Arab Emirates (UAE), I’ve been running a non-split version of my Access database on a terminal server with Access Runtime, and it’s incredibly slow compared to running it locally on a user’s machine. Here’s a bit of context:

The same database, when run on a local machine, performs perfectly fast, but when placed on the terminal server (with Access Runtime) and accessed by a single user, it becomes noticeably sluggish. This is the case even when there’s no split database involved, and no other linking or external factors that could cause this.
I’ve already worked with the IT team to troubleshoot, but nothing seems to solve the issue. Has anyone encountered something similar or have any suggestions on what might be causing this performance hit on the terminal server? Any ideas are welcome!

Thanks in advance!
Regards
Emmanuel Katto

 

[arnelgp]

of course it will be slow especially when the connection is miles away.

 

[The_Doc_Man]

there’s no split database involved, and no other linking or external factors that could cause this.

If the slowdown occurs when doing something in bulk, like getting a local printout of a report on the other end of the remote connection, then that is just network latency. It would depend on the speed of the slowest link between your local terminal and that remove server.

If even simple commands like single-record SQL statements are slow, then your "no other linking" statement might not be correct.

 

[Cotswold]

The FE should be on a local PCs and the BE accessed via TS. You also need the permanent table link between them. (plenty of stuff on the table link on the forum) I never had a problem with speed on TS and Runtime and ACCDB, or MDB. I've had over 50 users on three remote sites on TS without complaints. Your network guys need to know what they are doing, mediocre isn't good enough.