Experts:
I would like to get some assistance with "pushing" a modified Access frontend (FE) from a LAN to client machines using "AutoUpdater" (posted on http://www.utteraccess.com/forum/Eas...r-t304808.html).
Please note that I previously opened similar thread related to this topic. Several experts recommended a different utility tool vs. AutoUpdater. I was totally open to trying out the alternate utility tools. Although all experts were extremly patient and provided continued assistance over the Thanksgiving weekend, I ultimately was never able to get the process to work (post had nearly 50 back-and-forth responses).
So, at this time, the focus on this new (re-focused) thread is to assist me w/ modifying AutoUpdater. However, if someone were to provide a **fully functioning** utility tool which allows me to push a modified FE to a client machine, I certainly would consider that one, too.
Please find attached .ZIP file containing "AutoUpdater"... allow me to provide some background and setup instructions first though.
Background:
- Attached .zip includes folder "Test" and two subfolders: "01_Server" and "02_Client"
- Subfolder "01_Server" includes two Access files: "Database_be" and "Database_fe". These databases are for testing the "pushing" server FE to the client machine only. Thus, the data in table "T_Branches" are dummy data and of no importance.
- Subfolder "02_Client" includes two Access files: "AutoUpdater" and "Database_fe".
Setup for Database_fe (in 01_Server):
1. Go to subfolder "01_Server" and open "Database_fe".
2. Delete linked table "T_Branches".
3. Now, re-link "T_Branches" via Linked Table Manager. Point to Database_be (01_Server) during the re-linking process.
4. FYI... please note this version of "Database_fe" includes 1 query object, 1 form object, 1 reports objects. Also, please note the value of "2" in tblLocalVariables.
Setup for Database_fe (in 02_Client):
1. Go to subfolder "02_Client" and open "Database_fe".
2. Delete linked table "T_Branches".
3. Now, re-link "T_Branches" via Linked Table Manager. Point to Database_be (01_Server) during the re-linking process.
4. FYI... please note this version of "Database_fe" does **NOT** include any query, form or report object. Also, please note the value of "1" in tblLocalVariables. Thus, missing the query, form, and report objects, it mimics an out-of-date FE version.
Setup for "AutoUpdater" (in 02_Client):
1. Go to subfolder "02_Client".
2. Press and hold "Shift" key; then open "AutoUpdater".
3. Delete linked table "tblLocalVariables".
4. Now, re-link "tblLocalVariables" via Linked Table Manager. Point to Database_fe (01_Server) during the re-linking process. Again, this is the FRONTEND on the server.
5. Finally, open up "frmSetup". In the first two (2) text boxes, select the FEs from both server and client, respectively. In the 3rd file path, please select your Access application or shortcut to Access. Then "Saves Changes".
6. In the last two (2) boxes you should see a "2" for the server FE and a "1" for the client FE.
7. Close "AutoUpdater".
Envisioned process:
- In a hypothetical scenario, the FE on the server has been modified. In this example, it is version "2" in tblLocalVariables.
- At the same time, the user/client still has the old FE (i.e., version "1" in tblLocalVariables).
- AutoUpdate shall "push" (or "pull") the modified FE version from server to client machine.
- Later on, I will rename "AutoLoader" (or its shortcut) with my actual database's name. If so, the database user "believes" he opens the actual client database but in reality open the AutoUpdater utility first.
- AutoUpdater will then check whether or not there's a newer version of the FE on the server. In this case, the answer is yes. Thus, client FE (v1) will be replaced with server FE (v2).
- Whether or not a newer FE was downloaded from the server, I then want AutoUpdater to invoke the process of opening up the "real" client database (i.e., Database_fe on client). So, ultimately, even though the user started by opening AutoUpdater (unbeknownst to them), they end up with the actual database being opened.
Existing issues:
- At this time, I get an error message "Invalid Procedure call or argument" after the FE has been downloaded. If both versions were the same, I get this error immediately. How can I fix this error?
- Also, the Database_fe on client is not opened by AutoUpdater. How should the code be modified to accomplish this?
Ultimate goal:
- User has both FE and AutoUpdater on client machine.
- System administrator makes a change to FE on server.
- User opens AutoUpdater (w/ renamed shortcut to mimic as if it's client FE). AutoUpdater utility compares both FE versions.
- If FE versions are the same, FE on client opened is opened by AutoUpdater. If FE versions are different, server is FE is download to client and then AutoUpdater opens the latest client FE.
Again, at this time in have two (2) existing issues that require modification.
Thank you in advance,
EEH