SadOldGoth
Programmer
Hi Folks,
I'm running a multi-user database(Access 2000) in a citrix environment. The database is split into back- and front-end pieces with the front end running as a .mde. This mde is called via hyperlink from another access mde - this is because we needed a way to launch the application as easily as possible - under citrix there are problems with file association and whatnot, and this proved to be the easiest solution, having all databases launched from a central app.
When everything works, it all works beautifully.
Trouble is, I'm getting some really strange stuff occurring, messages such as 'Cannot find path ...', 'Some files contain viruses', 'database needs to be repaired', etc. Now, if any of the above messages were actually true I wouldn't mind, but they're not. If I get all my users to log out, and then get them to log back in again, everything is groovy.
The problem, I think, is down to the lock file getting confused when any one user logs out, because nobody can get back in again.
Does anyone have any ideas that might shed some light on what is happening, and, ideally, some way of solving the problem?
I'll be converting the back-end to SQL in the very near future, but I'm not convinced that will solve the problem.
Thanks,
Jes
I'm running a multi-user database(Access 2000) in a citrix environment. The database is split into back- and front-end pieces with the front end running as a .mde. This mde is called via hyperlink from another access mde - this is because we needed a way to launch the application as easily as possible - under citrix there are problems with file association and whatnot, and this proved to be the easiest solution, having all databases launched from a central app.
When everything works, it all works beautifully.
Trouble is, I'm getting some really strange stuff occurring, messages such as 'Cannot find path ...', 'Some files contain viruses', 'database needs to be repaired', etc. Now, if any of the above messages were actually true I wouldn't mind, but they're not. If I get all my users to log out, and then get them to log back in again, everything is groovy.
The problem, I think, is down to the lock file getting confused when any one user logs out, because nobody can get back in again.
Does anyone have any ideas that might shed some light on what is happening, and, ideally, some way of solving the problem?
I'll be converting the back-end to SQL in the very near future, but I'm not convinced that will solve the problem.
Thanks,
Jes