I have a split Access db which my users run in Access Runtime. On installation I have the backend located in the same directory as the front-end.
I would like to allow users to install on a peer to peer or network and open the program with the same backend file. (share the data over the network)
I need to find a VERY user friendly way to allow the end user to install the program on each workstation and automatically connect to the shared backend file.
I have looked at the FAQ on Relinking Tables in Runtime, but 1) I don't think this is a relinking issue and 2) that method looked very complex and way above my skill. (I am not a full time programmer)
My first thought is to have the end user install the front end on one machine in a peer to peer situation. The problem is that if the user runs the db from a workstation by launching it from its peer the db will not launch as it will not locate the backend which it expects to find on the local drive.
This should be simple, but maybe I have just been knocking at the wrong door?
I would like to allow users to install on a peer to peer or network and open the program with the same backend file. (share the data over the network)
I need to find a VERY user friendly way to allow the end user to install the program on each workstation and automatically connect to the shared backend file.
I have looked at the FAQ on Relinking Tables in Runtime, but 1) I don't think this is a relinking issue and 2) that method looked very complex and way above my skill. (I am not a full time programmer)
My first thought is to have the end user install the front end on one machine in a peer to peer situation. The problem is that if the user runs the db from a workstation by launching it from its peer the db will not launch as it will not locate the backend which it expects to find on the local drive.
This should be simple, but maybe I have just been knocking at the wrong door?
