Hi,
I have a system running in a large organization, 1-3 users, FEs on each work station, BE on a LAN network drive. Using Acc2002 mdb files in Office 2010-13 environment.
The user occasionally gets a few unexpected error messages.
- Some are about the BE file format, indicating file corruption, that I solve by compact & repairing the BE.
Others of unexpected data update error messages:
- This is the Hebrew version of the message indicating records can't be added to a table, do to Index or Data Type constraints. There were no constraint violations (Please note the two 0s in the top row). It occurs during a data manipulation process, containing a few UPDATE and INSERT queries. Please trust - the data obeyed all constraints.
View attachment 87964
- The 'Application defined or object defined error' while VBA runtime.
- 'Data mismatch' in key error.
- Write Conflict.
Again: these occasional errors occur in a closed process, working fine for years, there's nothing in the data or logic that should fire these errors.
I suspect it is the organization's LAN: If it was moved to the cloud, wold that cause errors of this sort?
Thanks in advance!
I have a system running in a large organization, 1-3 users, FEs on each work station, BE on a LAN network drive. Using Acc2002 mdb files in Office 2010-13 environment.
The user occasionally gets a few unexpected error messages.
- Some are about the BE file format, indicating file corruption, that I solve by compact & repairing the BE.
Others of unexpected data update error messages:
- This is the Hebrew version of the message indicating records can't be added to a table, do to Index or Data Type constraints. There were no constraint violations (Please note the two 0s in the top row). It occurs during a data manipulation process, containing a few UPDATE and INSERT queries. Please trust - the data obeyed all constraints.
View attachment 87964
- The 'Application defined or object defined error' while VBA runtime.
- 'Data mismatch' in key error.
- Write Conflict.
Again: these occasional errors occur in a closed process, working fine for years, there's nothing in the data or logic that should fire these errors.
I suspect it is the organization's LAN: If it was moved to the cloud, wold that cause errors of this sort?
Thanks in advance!