I have recently been experimenting with adding an Access database to a shared folder (in a network HomeGroup) and have it working on two networked PCs. Then tried the same with the database split but I get a path error on the PC joined to the HomeGroup (where the database resides) whenever the backend (tables) are accessed by a form or from the Tables listing. If I however open the backend file directly from the file directory, the tables all open as expected.
The path stated as being invalid in the error message starts with "C:\Users\etc..... instead of \\LAF-PC\Users\etc..... so it looks (to me at least) that it is attempting to load the file from the local hard drive rather than the host computer.
I don't know if I've explained that in a comprehensible manner but would appreciate any hints as to why a split database works differently in this situation than a non-split.
The path stated as being invalid in the error message starts with "C:\Users\etc..... instead of \\LAF-PC\Users\etc..... so it looks (to me at least) that it is attempting to load the file from the local hard drive rather than the host computer.
I don't know if I've explained that in a comprehensible manner but would appreciate any hints as to why a split database works differently in this situation than a non-split.