Running MDE file over Citrix

[Blaize]

We are having locked database issues with having an MDE file which we added for our Citrix users. The Citrix users are added to a specific group in Active Directory which allows them to access the MDE file. Works fine for the first person to access the MDE file, if someone else connects up to Citrix and clicks on the shortcut they get a message advising the database is locked out.

We have found that adding the MDE file into a couple of users Terminal Services Profile they are able to access the Database but as the MDE file is 60mb this is having an effect on the disk space. To compound this we need to roll it out to approx 10 people. Does anyone know of a way round this?

[MMcCarthy]

It sounds like the database is set to exclusive rather than shared.

Not sure if this tool is still available in your mde. If it is it would be under Tools - Options and under the Advanced tab.

If not try getting the users to set the default open mode of their Access application to shared (same setting)

Only other option would be to use the source mdb file to make the change and recreate the mde.

[Blaize]

Hi thanks for the reply, unfortunately both the front and back end default open mode are already set to shared. It’s bizarre as it works fine over the network just in Citrix we have the issue.

[MMcCarthy]

Coincidentally I had a similar problem on a client site today although it wasn't with citrix. There were issues with the network whereby the database being opened using the shortcut produced a database not found error.

I found that opening Access first before clicking on the shortcut solved this problem. I still don't know what caused it other than the speed of the two stations with this problem was very slow over the network.

I concluded that Access was trying to open the database as the application opened and due to the slow network speed it couldn't find the database before the application was fully opened thereby producing the database not found error. However, if the Access application was opened first then the link worked just fine. It also worked if the user searched for the database using the applications open dialog.

These are strange errors that I haven't seen before but by some strange coincidence I saw today for the first time.