If the application and data are not kept separate there is a huge chance of data loss which we explain through examples. We also explain how separating the application from data can be of help in keeping data safe.
Out of all the precious things that we fear losing one of the most precious is important data. This data can be the one you are using for personal reasons or company data which you are responsible for managing. So if you lose the important company data, you will not only be in for a shock but might also end up losing your job. There are several different issues that might cause you to lose the data contained in your Access application without any obvious mistakes or errors you made.
You can imagine what a nightmare it would be if you spend hours making changes in a database and updating it, and a day later come back to find the database the way it was before you made all those changes. To save yourself from this nightmare, we would suggest you to separate your data from the application. Now for those of you who think that we are asking you to separate the data stored in MS Access from Access itself, you are wrong. We are not suggesting you that, but a simpler and intelligent solution.
Splitting Access Databases for separating Data from Application
The suggestion of keeping the data separate from application means dividing or splitting your Access database into backend and frontend. This will separate all your user interface objects from the ones that are not a part of the user interface. Thus creating a distinction between objects like forms, reports, and queries, which are available in the frontend, and the data tables which are present in the backend.
So whoever needs to use the objects will be provided access to the frontend, whereas those with permissions to make changes in the tables will be provided access to the backend. This will not only keep data safe by limiting user access, but will also ensure greater safety by retaining all the changes made in the backend, and later implemented in the front end.
Why you should opt for Separating Application from Data
When you have all the user interface objects in the frontend along with the links to the tables in the backend, you can play with the objects as much as you want and then connect the updated file with the frontend, thus incorporating all the changes you made. Untill the time yo have not connected the updated file, you will still be operating on the old file without the changes.
Since the frontend of the database provides you with links to the backend you can ensure that none of the changes are saved till the updates are made in the backend. Since all the crucial data is contained in the backend and the frontend is only containing the links to those crucial pieces of information. This process is termed as splitting the database, linking the backend and frontend, and is also described as the process of separating the application from the data. It goes a long way in making an Access recovery operation easy and successful in quick time.
Vivian Stevens is a data recovery expert in DataNumen, Inc., which is the world leader in data recovery technologies, including SQL Server recovery and excel recovery software products. For more information visit www.datanumen.com