mlcktmguy
asked on
Access Citrix Instalation
I know this is a longshot since I'm posting in an Access forum but I promised my IT person I would ask for input. I have installed an Access 2003 application on the clients network. The front end is an MDE and the data backend is an MDB resident on the server. The installation is handled by Sagekey.
We have dozens of clients set up with this same configuration. In those cases each user has a copy of the app on their local machine and the data is resident on the server.
Half of the user for the new client are set up in a similar manner, local copy on tier machine, linked to data on the server. Those users are fine. However, this client also has a satellite office with the other half of the users. The satellite users come into the system using Citrix. I don't know Citrix and I am not a communication person but I'll try to relay this as best as I can. As explained to me, on the cirtix side there are two servers the users come in to one or the other. Our application is installed on each server, one time. That means that multiple Citrix users are using the same MDE. A a rule we offload as much as possible to the clients and use local tables to process the selected data. As you might guess, with multiple users using the same MDE, the local tables aren't functioning as they should. If 2 users are using the same local table in the same MDE their data becomes intermingled and the results are incorrect.
My first suggestion was to install a local copy on each machine of the satellite users. The IT person is hesitant to do this because he feels having them connect thru a VPN (whatever that is) would not provide adequate response.
My question: Have any of you EE'ers installed you apps in similar circumstances? If so, what kind of architecture did you use for the remote users?
We have dozens of clients set up with this same configuration. In those cases each user has a copy of the app on their local machine and the data is resident on the server.
Half of the user for the new client are set up in a similar manner, local copy on tier machine, linked to data on the server. Those users are fine. However, this client also has a satellite office with the other half of the users. The satellite users come into the system using Citrix. I don't know Citrix and I am not a communication person but I'll try to relay this as best as I can. As explained to me, on the cirtix side there are two servers the users come in to one or the other. Our application is installed on each server, one time. That means that multiple Citrix users are using the same MDE. A a rule we offload as much as possible to the clients and use local tables to process the selected data. As you might guess, with multiple users using the same MDE, the local tables aren't functioning as they should. If 2 users are using the same local table in the same MDE their data becomes intermingled and the results are incorrect.
My first suggestion was to install a local copy on each machine of the satellite users. The IT person is hesitant to do this because he feels having them connect thru a VPN (whatever that is) would not provide adequate response.
My question: Have any of you EE'ers installed you apps in similar circumstances? If so, what kind of architecture did you use for the remote users?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks you for the suggestions, I passed Gutav's response on to the IT people and they are working thru it. With some modificaton since we have a Sagekey installer. Sagekey takes care of putting the runtime on the machine and setting up everything to run.
MY suggestion was to adapt Gutav's approach putting an Icon on the users desktop that points to the Sagekey installer on the server. They would use that to get into the app. It would refresh/reinstall each time they entered but that's not a big issue since they only log on once a day. This would also ensure that they always had the most recent version of the application.
The IT people said it failed because the user did not have adequate authority to install and the are reluctant to give it to them.
I suggested setting the 'Run as Adminstrator' property of the desktop icon so they owuld have authority. I heard that is giving issues also but haven't gotten the specific yet.
Any ideas on your part Gustav?
MY suggestion was to adapt Gutav's approach putting an Icon on the users desktop that points to the Sagekey installer on the server. They would use that to get into the app. It would refresh/reinstall each time they entered but that's not a big issue since they only log on once a day. This would also ensure that they always had the most recent version of the application.
The IT people said it failed because the user did not have adequate authority to install and the are reluctant to give it to them.
I suggested setting the 'Run as Adminstrator' property of the desktop icon so they owuld have authority. I heard that is giving issues also but haven't gotten the specific yet.
Any ideas on your part Gustav?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Gustav, thank you so much. This was becoming a huge problem. I have a lot of Access experience but I am lost in the communication/network world. The IT person really had no idea how to resolve this but we implemented your suggestions and the application is operating as it should for multiple users in the Citrix environment.
The advantage was, I did not use linked tables to the MySQL server. I used all Pass-Through Queries that included the necessary ODBC Connection string at the time they were run. Same with data entry, I used ADODB connections to update recordsets and released the connection when finished. Any laptop running in the field that had an internet connection could run the Access app with pretty much the same performance as the users back in the office. I was amazed at the performance to be honest.
Just another approach ...
ET