I’ve read most of the posts on splitting and deploying Access applications but most of them appear to concentrate on networked backend databases. However, my case is slightly different and I would like somebody to confirm that I’m taking the best course of action to achieve my goals.
I’m currently developing a non-networked accommodation booking system which has some basic functionality that my end user is testing on their standalone PC. I am currently adding historic data to the data tables to allow the end users to make full use of their existing data when testing the new system. The application development is ongoing and I will be releasing updated versions of the system over the coming months and want to be able to release the new features without having to reload the most up-to-date data from my user each time.
Therefore, is the best approach to:
Add the historic data to my development.
Split the Database giving front and backend databases.
Initially deploy both front and backend databases to the end user.
Continue with the development on the split system and when new features are added just deploy the front-end database to my users leaving their data tables in tact on their machine.
I’m currently developing a non-networked accommodation booking system which has some basic functionality that my end user is testing on their standalone PC. I am currently adding historic data to the data tables to allow the end users to make full use of their existing data when testing the new system. The application development is ongoing and I will be releasing updated versions of the system over the coming months and want to be able to release the new features without having to reload the most up-to-date data from my user each time.
Therefore, is the best approach to:
Add the historic data to my development.
Split the Database giving front and backend databases.
Initially deploy both front and backend databases to the end user.
Continue with the development on the split system and when new features are added just deploy the front-end database to my users leaving their data tables in tact on their machine.
