ahmed_optom
Registered User.
- Local time
- Today, 04:31
- Joined
- Oct 27, 2016
- Messages
- 93
I have an access FE, SQL BE.
Everything is working well, however as the system is getting bigger and busier we are now getting more and more write conflict issues.
This is where a warning pops up saying there is a write conflict, do you want to save, copy or drop changes. This is obvious hideous to see for a normal user.
What I would like to know, is there a way to design the forms such that there are no visible errors and the most recent update is written? I have searched and whilst there are threads on the topic, there isnt a clear strategy to avoid them.
I have looked at record locks and they dont appear to solve the issue. If i go from no locks to edited, all it does in reality is change the warning message.
What I am thinking is that if I redesign the forms so that there are no bound forms, would that solve the issue? This would be a large task, but I need to fix this.
What should the "proper" design be to avoid these conflicts ?
Thanks in advance
Everything is working well, however as the system is getting bigger and busier we are now getting more and more write conflict issues.
This is where a warning pops up saying there is a write conflict, do you want to save, copy or drop changes. This is obvious hideous to see for a normal user.
What I would like to know, is there a way to design the forms such that there are no visible errors and the most recent update is written? I have searched and whilst there are threads on the topic, there isnt a clear strategy to avoid them.
I have looked at record locks and they dont appear to solve the issue. If i go from no locks to edited, all it does in reality is change the warning message.
What I am thinking is that if I redesign the forms so that there are no bound forms, would that solve the issue? This would be a large task, but I need to fix this.
What should the "proper" design be to avoid these conflicts ?
Thanks in advance