Topics Search

Automatically Update the Front End of a Split Database

Automatically Update the Front End of a Split Database
Views: 1419
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:

More topics

 

Front end changes

Preview
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

Preview
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

Preview
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'.

Preview
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'.

Preview
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

Preview
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

Preview
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

Preview
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

Preview
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.
 

Problem distributing front end of database?

Preview
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?