Access frontend

[MarcusMaximus]

Hi, im new hear and at access programming for a ear now. I'm looking for ways to improve response time on or access CRM here inwork. Currently we have a frontend(forms and queries) and a backend(tables) stored on the file server, the users here(about 25) use access on terminal server.

i was wondering would it be benificial to move the front end of the database to the terminal server to reduce network traffic each time the user opens a new form or report etc, To improve response time and increase productivity etc. Is it a case that the entire frontend is loaded into RAM when they open the application and it wouldn't matter where its being loaded from or would it be benificial to have it loaded from the local C:\ drive of the terminal server so there not loading it accross the network each time.

thanks in advance

 

[The_Doc_Man]

Search this forum for "Terminal Server" and "CITRIX" to see threads on people who have tried to do what you describe. You might find some case studies that help you understand better what you are trying to do.

Note, however, that you need to consider what license you use for Access when a single copy of Access will simultaneously server multiple users. It is not built for that and can run into issues.

 

[HiTechCoach]

Hi, im new hear and at access programming for a ear now. I'm looking for ways to improve response time on or access CRM here inwork. Currently we have a frontend(forms and queries) and a backend(tables) stored on the file server, the users here(about 25) use access on terminal server.

i was wondering would it be benificial to move the front end of the database to the terminal server to reduce network traffic each time the user opens a new form or report etc, To improve response time and increase productivity etc. Is it a case that the entire frontend is loaded into RAM when they open the application and it wouldn't matter where its being loaded from or would it be benificial to have it loaded from the local C:\ drive of the terminal server so there not loading it accross the network each time.

thanks in advance

It is generally always better to have the front end on he local hard drive. Every user should always have their own copy of the front end so that it is NOT shared. Even with terminal server.

If you really want to cut down on network traffic, place the back end on the terminal server also. This way everything is local.