The one time I dealt with this situation was years ago, but we had a "nightmare" data sharing setup in which Access linked to an Excel worksheet as a table and it was always running into trouble with the Engineering team trying to update it through Excel while the Sys Admin team was trying to update something else through Access. Data corruption got slung all over the place like a monkey-cage riot at the zoo.
We finally solved the problem by telling the Engineering team that Excel was bollixing up the works because it didn't share quite as nicely with others as would Access. I had to rebuild the table they were using and take into account that as it was originally a spreadsheet, it was denormalized to Hell and gone. That was three months of redesign and migrating a little bit at a time to make it behave in a way that came closer to satisfying everyone. I never could make it work perfectly because I was not allowed to finish the project.
Of course, the Engineers hated it anyway because it was no longer "their spreadsheet" - but the Navy told them that what HAD been happening was "unsat" and that it was time to do something else, so "live with it and get on to other business." The upshot of that was that I was persona non grata because I had to fix their problem in a way that they could not. If you know about the "Not Invented Here" (NIH) syndrome, you will understand.