Automatically Update the Front End of a Split Database

A multiuser database should be split into a front end and back end. (For reasons why, please see the gem tip: Split the Database.) The back end will contain the tables and relationships. The front end of your database will contain the application objects: queries, forms, reports, macros, modules and any local tables. The front end will include the links to the tables contained in the back end database.

Sponsored Links:

Related Topics

Front end changes
Frequent reader first time poster. I'm relatively new to access so I'm trying to wrap my mind around this. I split my database and will have each user store the front end on their individual PC.

When I need to update the front end how does this work? Let's say I'm editing the front end on my pc. And will itwork as long as I don't change the file name? Or should I be changing the file name and relinking it? What happens if some people keep using the old front end? Its hurting my brain to thinkhow this works.


MOdifying forms in split database
I have a access 2010 split database and I need to modify one form on the front end (it is an accde file).
However, when I open the Front end, I cannot find the possibility to go into the form design mode.

how do I need to do it? do I need to restart from the unsplit database?

PS: the both the front end and the back end are password protected.


Split database
This must be a silly question, but isn't the purpose of a split database to separate the front end and the back end? Then why am I still able to see the tables in the navigation pane in the front end even after splitting it? I was thinking if I split it, then the entire table will be in some other location I specified and data will be stored and retrieved from that location. Any thoughts on how to get rid of the table in the front end?

I know that hiding the table is an option, but still an user who knows his way around will be able to manipulate


Split-Database. Keeping the front-end 'private'.
I want to create a split-database. I want the entries made on the front-end to update into a combined table in the back-end.

Back-end: One table with everyones entry

Front-end: Multiple forms that feed into the back-end.

When person A accesses his front-end form, he can only see his entries.

When person B accesses his front-end form, he can only see his entries.

When manager A wants to look at the back-end, he can see everyones entry in one table


Split-Database. Keeping the front-end 'private'.
I want to create a split-database. I want the entries made on the front-end to update into a combined table in the back-end.

Back-end: One table with everyones entry

Front-end: Multiple forms that feed into the back-end.

When person A accesses his front-end form, he can only see his entries.

When person B accesses his front-end form, he can only see his entries.

When manager A wants to look at the back-end, he can see everyones entry in one table.


Version Updates
I have a database that I have split between a front end and backend. I have several users who will have copies of the front end on their computers, and I would like to make it easy to just update from the program, rather than risking them using old versions because they don't check their email. Is there a way to have the program check for an updated version on the server, then automatically replace the old file with the new one?


deployment
what;s the best way to deploy a database? like, when they install the database, it is automatically split and other workstations can automatically link to the back end of the db when they have the front end in their desktops


How to make new back-end tables visible to front-ends
I have an Access 2007 database that has been split into a front-end and a back-end and has been working quite well. On occasion, I have a need to add a table to the back-end, but I don't know how to make such tables visible to the front-end(s).

Newly added tables to the back-end do not automatically appear in Linked Table Manager when I open the front-end.


Shortcut to front end for terminal server users
I have a split and shared database for my company, but not all users can use the system. Why?

Access 2010
Split database
Front & back ends saved on shared drive
Shortcut on terminal server - Maybe shortcut is wrong?
Shared database, not exclusive

I have read somewhere that each user should have the front end saved to their computer, but I'm not sure this applies as the front end is currently on a shared drive. Also, surely space and memory wise, this isn't helpful? What happens when you want to update the front end - does everyone have to resave the new copy?

Some users can use the system no problem, but other get an error code of: "Invalid database object reference".

Please help me as I'm really not sure what to do for the best.


Finding back end database and linkin' to a front end
I'm creating a system, using front-end forms, queries, reports and a back-end just to store the data in tables.

There should be two setup files for the final customer: one is for full installation of the front end and the database. Then, the second should be used for the installation of the front end, only, on other PC terminals.

When installing the front end only version, the code will automatically search for the database in THE COMPUTER, including network mapped drives. Once it's found, the selected databasetables are linked to the front end.

The problem is: In great HD drives that search could take longer than expected, something like several hours.

got a solution for linking the database automatically, or for smarter searching of the COMPUTER?


Problem distributing front end of database?
This is my first database and I have split it, placed the BE on a network drive, and emailed the FE which was made into an accde file, which works great on my computer that it was made on.However, when my other user tried to open it, there was a message about it not being a valid path? Do I have to map the drive it's on to every computer the front end will be used on?

Also, I have a copy of the database saved before it was split, but if I make changes to the forms in this old file, how do I replace the old FE with the new one while still connecting it to the old BE so the data is saved? If I split the database again, won't the new front end be connected to the new back end?


Split Databases
I have a database which I have split front end and back end. When some users are accessing the front end, it is locking the database - both front and back. It doesn't happen every time a user is in the database - seems very ad hoc as to when it happens. Does anyone have any ideas how I can prevent this happening. I had used a similar set up last year and it worked fine once we had ironed out teething problems for users being able to access it but never had this issue arising


When to split
I am creating a simple database to track history on electronic machines. The database will be used by several staff +-5 to10. Any advice on things to do when I have this many people connecting would be appreciated.

Also, I am currently designing the db as a single entity, but will have to split at some point in time. I would like to know when I should split ? right from the start of design or should I get everything working first before splitting ?

I would also need someway of the front end checking the path to the back end and if it is not valid then to ask the user to enter the path using the common dialog that generally pops up when you open a file through a program interface.

The new path would then be saved to the front end and checked on every occasion the front end is opened.


Union Queries when Splitting Database
I am trying to split a fairly complicated database (~10 tables, with ~10 enforced relationships, etcetera). A bit part of the design is a union query that mediates between three tables, into a fourth.

I need to split the database so that I can distribute the front end around to other users. In order to split, I believe I have to delete the union query (because otherwise it "can't find the object" when I try to split).

This seems like it would be fine, because I can just go back and remake the union query after the split right? But how exactly does that work? I do it in the back end and the front end


VBA code to check for updated front-end
I have a front-end database that I deploy to a team. From time to time I need to re-deploy an updated front-end, to add features or fix bugs. Currently that involves me either manuallyupdating everyone, or sending instructions around that some of the less tech-savvy folks have trouble following.

I thought of trying to build in an auto-update feature into my front-end (that could run on the Form_Load event), but not clear on how it might work. I definitely know how to code it so that it would look for a more recent version of the front-end on the network drive and copy the updated front-end to the user's local machine if it found an update.

But is there a way tohave the old front-end (which is the one that is open and running the code) close itself and delete itself, and then to launch the new front-end?


Questions about splitting a 2010 Access database
I have read through some of the other threads on this subject and I am more confused than ever.

I have split an Access 2010 database with the tables being in the backend. Some of these tables were originally imported from an Accounting database. Before I split the database, I had aseries of macros that would delete these "Accounting tables" and then import the latest version of these tables from the accounting database.

I need to continue to update those tables on an on-going basis. As a result, I created a startup form that had a control to backup the database and another control to run the macros to update the accounting tables.

I then opened the front end and relinked all of the tables in the back end to the front end.

From what I have read, I believe that I should not have done that (I.e. the backend should contain tables only- no macros, forms, etc.). If that is correct, what is the proper way to deal with these tables that need to be replaced on an ongoing basis? I know I can link the accounting tables from the accounting database to tables in the backend (rather than import them) but Iwould rather not do that for a variety of reasons.

can I use VBA or macros or something in the front end to do these updates at a click of a button?


Working on a split database at home
I have a split database at work and it is working correctly.

I copied the front-end and the back-end to a flash-drive. I then copied both of the files from my flash-drive to my home computer.

I can open the back-end database and it shows all of the tables but, I can't open the front-end database.

I have opened the back-end an imported all forms, reports, queries, and macros from the front-end database. But I can't open it?

If I do any work will I have to split the database again so I can updated the databases at work?


Working on a split database at home
I have a split database at work and it is working correctly.

I copied the front-end and the back-end to a flash-drive. I then copied both of the files from my flash-drive to my home computer.

I can open the back-end database and it shows all of the tables but, I can't open the front-end database. I was planning on doing some work this weekend.

I have opened the back-end an imported all forms, reports, queries, and macros from the front-end database. But I can't open it?

If I do any work will I have to split the database again so I can updated the databases at work?


Split Database having Linked Tables
I am having a database in which the tables are linked to mysql tables which are located in a server. Now I want to split the database. After I split the database, I get front-end and back-end database. In the front-end , how can I link the to the database which is already having linked tables.? I hope I posted the question right. Basically, linking to a datbase which is already having linked tables. How do we do it?


User level security and splitting databse
I have access database. I want to have user level security on it and split database- and have it on local network.
Do I install uls first or split?
I read if you split database - users can drag copy of front end to their desktops- does that mean they drag the front end database and shorcut created to log on?
If you already split database - and wanted user level security would you have to have it on both databases