jadeverell
Registered User.
- Local time
- Today, 03:22
- Joined
- Nov 23, 2007
- Messages
- 14
Splitting a Database (merged thread)
Hi,
I am after some advice please, I have the following set up with regards to a shared database (Stored on a network, and used by several users) I have created:
MDB File - This contains all the forms/queries/reports etc
MDE File - Same as above but with restrictions on editing forms
I then go on to 'Split' the MDE file into a Back End and Front end, which is distributed to people that use the database.
My question is; after i make my design changes in the MDB file (master file) and go on to create a new MDE file (and then import the old tables into the new MDE file), Do I need to split the new MDE file again (into a front end and back end), or does it automatically link to the tables in the previous Back End system?
I know it seems quite complicated but it seems to work quite well...
I hope you can offer some advice.
James
Hi,
I am after some advice please, with regards to my shared database (stored on a network, with several users) I created:
I have the following set up within a multi-user environment:
MDB File - Stores all the forms/reports/queries etc
MDE File - Same as above but with Edit restrictions
I then go on the 'Split' the database into a Back-End and Front-End system, and distribute the FE system to all users that access the database.
My question is; Once i make design changes to the original MDB files and then create a new MDE file, do i need to split the database every time, or does the newly created MDE automatically link to the previous Back-End tables once i import all the tables from the old MDE file?
I know this is slightly confusing, but the system seems to work.
I hope you can offer some advice on this matter.
Thanks
James
Hi,
I am after some advice please, I have the following set up with regards to a shared database (Stored on a network, and used by several users) I have created:
MDB File - This contains all the forms/queries/reports etc
MDE File - Same as above but with restrictions on editing forms
I then go on to 'Split' the MDE file into a Back End and Front end, which is distributed to people that use the database.
My question is; after i make my design changes in the MDB file (master file) and go on to create a new MDE file (and then import the old tables into the new MDE file), Do I need to split the new MDE file again (into a front end and back end), or does it automatically link to the tables in the previous Back End system?
I know it seems quite complicated but it seems to work quite well...
I hope you can offer some advice.
James
Hi,
I am after some advice please, with regards to my shared database (stored on a network, with several users) I created:
I have the following set up within a multi-user environment:
MDB File - Stores all the forms/reports/queries etc
MDE File - Same as above but with Edit restrictions
I then go on the 'Split' the database into a Back-End and Front-End system, and distribute the FE system to all users that access the database.
My question is; Once i make design changes to the original MDB files and then create a new MDE file, do i need to split the database every time, or does the newly created MDE automatically link to the previous Back-End tables once i import all the tables from the old MDE file?
I know this is slightly confusing, but the system seems to work.
I hope you can offer some advice on this matter.
Thanks
James
Last edited by a moderator: