Hello everyone.
With my new application I have already released to my colleagues I 'm facing one big issue which never happened before with all my applications.
Users are connecting to the backend database through frontend installled on their desktop. There are maxiumum 6 users working with database at the same time.
Almost everyday backend database is suddenly getting inconsistent state.
When this happen I need to open backend database and execute compact&repair.
Do you have any idea why my database is getting inconsistent state? Is there any smart way to find a root cause?
In case there is no way to eliminate root cause, maybe is it possible to trigger compact&repair automatically while the user close the frontend?
There is also one constraint: all my users have only runtime installed (no Access full version is available on their PC's).
Thanks in advance for your support.
With my new application I have already released to my colleagues I 'm facing one big issue which never happened before with all my applications.
Users are connecting to the backend database through frontend installled on their desktop. There are maxiumum 6 users working with database at the same time.
Almost everyday backend database is suddenly getting inconsistent state.
When this happen I need to open backend database and execute compact&repair.
Do you have any idea why my database is getting inconsistent state? Is there any smart way to find a root cause?
In case there is no way to eliminate root cause, maybe is it possible to trigger compact&repair automatically while the user close the frontend?
There is also one constraint: all my users have only runtime installed (no Access full version is available on their PC's).
Thanks in advance for your support.