Good morning everyone.
We have a large split database, where the backend resides on a nas and 3 - 4 users have the front end on the desktop.
The front end is version controlled so everyone is running the same front end.
We recently moved the file systems from a NAS to a Debian server with SAMBA shares - I don't see this causing any issues as the SMB2 drive maps are routine.
During the working day, we can have a couple of errors where the DB falls into an unrecognised format. The usual recover compact and repair works.
This morning, I was updating an existing record and my colleague next to me also had this record in view but was not editing it. I noticed that after I had updated the record and left the record that it had not updated in her view. I waited a few seconds then the unrecognised database format error occurred.
So the record set was not updated and something went wrong.
We have also had this issue where a record data was replaced with #'s - very dangerous.
The database has been in development for around 15 yeas, so most likely originally built in office 2003. We are now using a plethora of versions, 2017, 2019, 2021. 2021 is the most recent addition which coincided with the move to the new server.
Could this be an office version conflict? Or likely something else I'm missing?
We have a large split database, where the backend resides on a nas and 3 - 4 users have the front end on the desktop.
The front end is version controlled so everyone is running the same front end.
We recently moved the file systems from a NAS to a Debian server with SAMBA shares - I don't see this causing any issues as the SMB2 drive maps are routine.
During the working day, we can have a couple of errors where the DB falls into an unrecognised format. The usual recover compact and repair works.
This morning, I was updating an existing record and my colleague next to me also had this record in view but was not editing it. I noticed that after I had updated the record and left the record that it had not updated in her view. I waited a few seconds then the unrecognised database format error occurred.
So the record set was not updated and something went wrong.
We have also had this issue where a record data was replaced with #'s - very dangerous.
The database has been in development for around 15 yeas, so most likely originally built in office 2003. We are now using a plethora of versions, 2017, 2019, 2021. 2021 is the most recent addition which coincided with the move to the new server.
Could this be an office version conflict? Or likely something else I'm missing?