Hi all, it was my first time today to split my database. It is a church software so it is to be packaged and distributed. It is an ms access 2007 db and I usually package using the usual ms access package wizard. When adding into the additional files, I usually include the accdb file but encrypt it with a password. Now I have two files, (that were created after the split) I need to create the .accdr file which I will package. I do not know if to only use the frontend split file, or how I will include the backend db that has the tables. Please help.
Question Split Database
- Thread starter HandSam
- Start date
DavidAtWork
Registered User.
- Local time
- Today, 11:38
- Joined
- Oct 25, 2011
- Messages
- 699
Unless all the users can access a server where the BE would be located, there's no point in splitting the database.
If you split the DB, it would be a maintenance nightmare.
David
If you split the DB, it would be a maintenance nightmare.
David
spikepl
Eledittingent Beliped
- Local time
- Today, 12:38
- Joined
- Nov 3, 2010
- Messages
- 6,142
It ain't necessarily so. Functionality can be added and many errors fixed by issuing a new front end, if the db is split. If not split, you need to get each user's data into the new version and THAT is a nightmare.
NeutronFlux
Registered User.
- Local time
- Today, 06:38
- Joined
- Aug 20, 2012
- Messages
- 78
When splitting an Access database, you get a FrontEnd (FE) and a BackEnd (BE). What you would probably do is put a password on your BE like you did before. By default, your FE has the location of your BE, although if you change the location of your BE, you will have to use the Linked Table Manager in the FE to link to the new BE location. Once everything is in the right place and linked, you can simply rename your FE from ".accdb" to ".accdr".
When updating, your BE is usually going to stay the same since you don't want the data there to be replaced. Instead, you just have to replace the FE. As for the package manager, I haven't really used it in a while. I do recall that there was an annoying issue where if you choose to bundle the Runtime, it will fail to install the whole package if the Runtime is already installed on that computer. I think it may also not have removed the registries for the installation, so you get multiple entries when you go to Add/Remove Programs.
Of course, if you are deploying it and want to make sure no one can tinker with it, you will need to take some extra steps, such as turning off special keys, navigation panes, compiling the FE, etc.
When updating, your BE is usually going to stay the same since you don't want the data there to be replaced. Instead, you just have to replace the FE. As for the package manager, I haven't really used it in a while. I do recall that there was an annoying issue where if you choose to bundle the Runtime, it will fail to install the whole package if the Runtime is already installed on that computer. I think it may also not have removed the registries for the installation, so you get multiple entries when you go to Add/Remove Programs.
Of course, if you are deploying it and want to make sure no one can tinker with it, you will need to take some extra steps, such as turning off special keys, navigation panes, compiling the FE, etc.
Similar threads
