I currently have a distributed app with a utility allowing the user to switch backend data files. This requires them to browse to a new location and select the file they want. This works great in the app. I want to add the ability for the user to be able to name the backend and then be able to select the location from a box using the name rather than have to browse for it each time.
I have included tblDataLocations in the frontend Athletic_Director.mdb file, but this file gets replaced each time a user updates, so permanent info here wouldn't be possible.
Ideally, you could write something that would check the backend database for tblDataLocations, and, if it doesn't exist, it would be created, but the backend can be in literally any location.
If you can't create the backend table, I need to create code that will allow the user to browse to the new backend file, name it and have the name they gave it and the datapath stored in the tblDataLocations. If they want to select a new backend, they will be presented with a form with the locations they have previously entered or they will have the ability to add a new location.
When the user exits the program, the information in the tblDataLocations needs to exported to a text file stored in the program folder. (Always C:\Program Files\Mansker Enterprises\AD).
When the user reopens the software it needs to check to see if there are records in the tblDataLocations table. If not, it needs to check to see if the text file exists. If it does, import the data into the tblDataLocations table. If not, do nothing.
the mdlSwitchBackend module in Athletic_Director.mdb is broken. It works fine in the full app, so I don't know if it's a missing reference or something else, so fixing this is included in the project.
Please ask any questions you may have