• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Split Access 2007 Database

Dahak

Dahak

Diamond Member
I have a client that is using an access 2k7 database that they need to share between 5-6 users. Im not personally familiar enough with access but I did find that you can split the database into a front end and back end components.

The main question that I have, is on the split database, if they need to change a the layout of the table or such, do you do the modifications on the front end or the back end?

From what I see in the help, as long as the front end is not compiled to a compiled binary file (an .accde file) they can add or make changes to the tables correct?

ie they had a table with the rows.
street address, street name, suite number, city, postal code .....

then split the database and they forgot to add a field for province the could correct?
 
Table corrections would need to be done in the back end, and then the front end would need to have the tables updated (through the linked table manager).
 
GeekDrew said:
Table corrections would need to be done in the back end, and then the front end would need to have the tables updated (through the linked table manager).
Click to expand...

Would that update through the linked tables manager, I would assume it would have to be done on each user correct?
 
Dahak said:
Would that update through the linked tables manager, I would assume it would have to be done on each user correct?
Click to expand...

It would have to be done on each instance of the front-end mdb. When I've encountered situations like this, I keep a "master" copy of the front-end on a server, and use a batch file to copy that front-end mdb down to the workstation, and launch that local copy, whenever the user wants to use the mdb. Then you only have to make changes in one front-end.
 
One last question in regards to the front end. if there is new queries or reports one in one of the front ends then I would assume that would have to copy that front end to all the users as well
 
Dahak said:
One last question in regards to the front end. if there is new queries or reports one in one of the front ends then I would assume that would have to copy that front end to all the users as well
Click to expand...

Yes, unless you are using a shared front end
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top