1
I am developing an application that runs from a shared folder. In the same folder is the Access database. To avoid conflicts in Access, it will only be allowed to run by only one user at a time, and two users of different machines will not be allowed to run the application at the same time.
I thought of a Usitan method, creating a temporary file every 5 min, containing the current date and time. Where, if another user tries to run the application and this file exists in the folder, its access is not allowed. And, if there is a bug in the execution of the first instance and the file stays in the folder, if it was created more than 5 min ago, a new access is allowed.
Is there any more 'elegant' method for this type of control?
I have the impression that any method will be Lusitan (or worse than that). The ideal would be to make a solution that does not depend on it.
– Maniero
But then would it be possible with the ms-access bank? It would have to migrate to Sqlserver?
– Leandro
I don’t think so. Access is a solution for very basic use. Even Sqlite is better than Access, although in this scenario it will be potentially problematic as well. It is a case that a server would be suitable.
– Maniero