Running Access on Citrix gives some user

[Scott95704]

I have an Access 2013 front end and sql server 2008 R2 backend. Users in our local office run a copy of the front end from their desktops without issue. Users in remote offices run the same file hosted on a Citrix server. Typically the first user to launch the file in Citrix has no problem, but subsequent users get a message that user admin has locked the file. Two things make this odd:
1. The front end was developed originally in Access 2003 and the 2003 version never caused this problem on Citrix.
2. A second database developed from the same bones is not having this problem. It was also an Access 2003 file upgraded to 2013.

I can launch multiple instances of the Access front end from Citrix and as long as I launch as second instance before my first instance fully loads, I do not get the locked file message, and neither do other subsequent users. This is currently how I am "clearing" the locked file.

I cannot tell if this problem is caused by a Citrix setting or an Access setting. I've done everything I can think of to make my two front ends identical, but still only have a problem with one of them.

[jforbes]

Instead of copying the Database to a common place and letting everyone execute the same File, I recommend that you copy the Database into each user's directory (like the Documents directory) and let them each run their own copy of the File. We use Terminal Server in this manner and it works great.

We also use a Batch file as the target of their Shortcut that checks for updates and grabs the latest Front End Database, if there is a newer one, and then launches the Database. Both of these threads, which are related, discuss this method:
Working with Front and Back-Ends
Feeding updates from a newer database version (1.1) to an older version (1.0)

[Scott95704]

Thank you jforbes! I've read a lot about this solution, and it does seem like the best way to address the issue. Does this solution require that each user have their own copy of Access? On Citrix the users do not need to have the app on their machines.

[jforbes]

I wouldn't be the authority on Licensing Office products on Citrix. And I don't typically have to worry about this in our environment as I happily get to transfer that worry to our capable IT department, but according to them, even though the code is installed and is being executed on the Terminal Server, Office is still a User based License, meaning each user needs a license of whatever they run.

Another option is to implement the Microsoft Access 2016 Runtime. We don't currently use it, but it is an option. We have shied away from it as there always seems to be some problem in getting the Runtime and a standard version working on the same computer. Which causes a lot of trouble in deployment as each machine can have either Office Pro or Office and the Access Runtime (this was just one scenario, at one point in time).

The point may be mute for you though. Access should be included in Office in the near future according to this link: Microsoft Access now included in Office 365 Business and Business Premium with new enhancements

I hope I have thoroughly muddied the water for you.