Incompatibility between Windows 7/Office 2013 and Windows10/Office 365?

[Erik I]

We have a small MS Access database shared between staff in an office on a network folder. Recently the company upgraded my computer to Windows 10 and Office 365. Now when I use the database, it sometimes causes it to fail for other users who are using Windows 7 and Office 2013. I didn't make any changes to the database structure or programming or anything.
When the other users try to open the database after I have used it, some of the symptoms they are seeing are: a small flickering window that appears when they first open it, having to click twice in a text box in a form to get the cursor to appear, and having the database crash (gives an error message and opens the VBA window) when trying an operation that involves VBA code.


Do you know what might be going on? Is this a known issue? Is there any good way to fix it (other than getting everyone on the same operating system or maybe splitting the database, which I don't really want to try)? (I tried reverting to a back-up of the database, which fixed the problem until I entered more data into one of the tables, then the problem came back again.)

[CJ_London]

Do you know what might be going on?

yes

Is this a known issue?

yes

Is there any good way to fix it

yes

(other than getting everyone on the same operating system or maybe splitting the database, which I don't really want to try)?

Splitting is the only way. Each user has their own copy of the front end on their local machine and the backend is located on the server. Any other way gives you the issues you describe, plus others such as total corruption.

[GinaWhipp]

I'm not sure what the aversion to splitting the database is but unless you split you will have issues.