I am trying to implement and distribute a .mde Access file split into front end (FE) and backend data (BE) files. This will allow me to perform FE updates with the user being able to maintain and back up their data.
I have tried the following and it seems to work:
1) Create the split db in a same named directory which will be added to the users drive on installation (this creates the link to the BE table)
2) Have the user copy and backup their backend file to another directory.
3) Have them install the new frontend and back end.
4) Have the user overwrite the newly installed backend db with their backup version. (while of course not changing the file name or directory location)
I have tested this and it seems to work fine.
Other than counting on the end user to perform this simple task (a mistake in itself!)are there any other pitfalls in doing it this way?
I have looked at some of the "solutions" for relinking to a backend db, and frankly they are very cumbersome and above my head. I need a simple solution which will allow end users to easily update their front end while maintaining their data backend.
Are there any other pit falls to this low tech solution?
I have tried the following and it seems to work:
1) Create the split db in a same named directory which will be added to the users drive on installation (this creates the link to the BE table)
2) Have the user copy and backup their backend file to another directory.
3) Have them install the new frontend and back end.
4) Have the user overwrite the newly installed backend db with their backup version. (while of course not changing the file name or directory location)
I have tested this and it seems to work fine.
Other than counting on the end user to perform this simple task (a mistake in itself!)are there any other pitfalls in doing it this way?
I have looked at some of the "solutions" for relinking to a backend db, and frankly they are very cumbersome and above my head. I need a simple solution which will allow end users to easily update their front end while maintaining their data backend.
Are there any other pit falls to this low tech solution?