Testing the Versioning Server
Follow these steps to test this solution:
- Make a copy of ClientApp.accdb and place it in another location.
- Open the original ClientApp.accdb and verify that you receive the message that says you are running version 1.0. Close ClientApp.accdb.
- Open VersioningServer.accdb.
- Open the USysAppHistory table in VersioningServer.accdb and add one record to the table. Make sure that the FilePath field points to the correct location of the copy of ClientApp.accdb.
ID VersionNumber VersionDescription FilePath 2 1.1 Minor update <PathTo>\UpdatedClientApp.accdb - Close VersioningServer.accdb.
- Open the copy of ClientApp.accdb and change the AppVersion database property to 1.1 to match the entry in the USysAppHistory table. Close the copy of ClientApp.accdb.
- Open the original ClientApp.accdb.
The frmCheckVersion form should open for a moment and then close. The updated version of the client application should open in a few seconds.
In this tutorial:
- Deployment
- Creating an Automated Build
- Design the Form
- Retrieving Information from the Source Database
- Building the Application
- Creating the Target Database
- Set Build Properties on the Target Database
- Setting Build Properties on the Source Database
- Deleting Data from Tables
- Calculating the Version Number
- Handling Application Dependencies
- Updating References
- Testing Reference Fix-Up
- Late Binding
- Licensing Your Applications
- Number of Records
- Restricting the Number of Times an Application is Launched
- Registering an Application
- Creating a Registration Web Service
- Validate the Registration Using the Web Service
- Miscellaneous Deployment Scenarios
- Create the Client Application
- Testing the Versioning Server
- Re-Linking Tables Automatically
- Programmatically Creating DSNs
- Creating a User DSN
- Ensuring an Application Runs Locally