Splitting a database

[fraser24]

Hi,

I have recently split my database using Access 2007 which has worked fine, but still feel unsure about how it all works from here and can't seem to find any information on what happens next. All the literature told me that when I split the database there would be tables in the BE and everything else in the FE but the tables are still showing in the FE with the link icon at the side, is this a new feature of 07 or am i mis-understanding.

• Do I keep the split FE copy as my copy (which is in the shared drive) or do I have this one or a copy in my local drive as well?
• When I make changes to the tables/forms etc is it just a case of sending the updated FE version to my colleagues?
• Is it possible to create a switchboard after the split or would I need to go back to my back-up copy to do this? (Have I split too early)
• What changes or additions can be made once a database has been split are you limited to what you can do

Kind regards
fraser24

 

[DCrake]

I am sure you will get alot of input on the splitting of databases. The main concept is that the back end database (Tables only) are resident in a shared location. The front end (all other objects) make up the user interface. This is distributed to all users who install it on their own workstation. The little arrows denote that a table is linked to a back end elsewhere.

Now heres the good bit. As a developer you will have your own copy of the front end, then when someone comes up and says "There is an error", or "can you get the app to do this.." you can make the modifications quite happily with out interfeering with the day to day useage of the application.

Make the mods, test it, agree it, distribute it. As the data is stored cetrally you only need to ensure that this is backed up.

Alot fall into the trap of splitting the database and placing both the FE and BE on a network and and provide shortcuts to the FE from the workstations. This defeats the object of the exercise.

There is plenty more on this subject to discuss but I will let other s contribute with their input.

 

[fraser24]

Thank you for your help, all information much appreciated.

Kind regards
Fraser24

 

[gemma-the-husky]

and yes, the tables DO still show in your database


black arrows identify linked jet tables

world symbols identify SQL tables

pretty little foxes identify FoxPro tables

-----------
you should note that there are a very few functions that wont work on a linked table - prinicipally using seek access on indexes.

 

[CharlesWilliams]

Having created and using a database that is split for the company I work for I would like to mention a few cavets I ran into. You might not encounter these yourself.

1. I agree with DCrake. you should not store the FE and BE on the server. The object of putting the database is to store the actual data in a database by itself. It would be good to store th FE on each computer. This leads me to my next point...

2. You should definitly keep a backup copy of the FE and BE in a safe place. Take it from from someone who has ran into this.

3. This one I don't think you'll run into this one but I have. If you have different people that have to priint to 1 certin network printer. I would keep a copy of each one in a safe place. Personal Example: At my co. we have the database on 2 different floors and I have to keep a copy of the FE from each floor. This is because the printer setup for forms and reports are setup differently for the copy one each floor.

4. I have found that updating co-workers computers with the FE has gotte to be a pain as I work with 6 other people and would need to update 12 computers with the FE.

If I can think of any thing else I'll post back. I'm looking forward to reading others opinions on this as I have been using a split database for about 12 years now.

 

[Galaxiom]

If you have different people that have to priint to 1 certin network printer. I would keep a copy of each one in a safe place.

You don't need different front ends for different users. User settings can be stored in a table.

You probably already have a table of users with a system to identify them at login. Store the name of their printer in that table too. Get the name of the printer and set it to a variable used in the print command.

I have found that updating co-workers computers with the FE has gotte to be a pain as I work with 6 other people and would need to update 12 computers with the FE.

Use AutoFEUpdater to distribute your FrontEnds.
http://autofeupdater.com/

 

[Galaxiom]

Pretty little foxes identify FoxPro tables

Sounds nice. I want to get FoxPro just for the link pictures.

I don't suppose there is a way users can change those pictures?

 

[The_Doc_Man]

As to the business of preventing people from running the FE from the shared location...

I have a startup form. It checks to see where it is... CurrentDB.name property tells me device, path, name, file type. Then I look at the BE file location. This is easier than you think. In any of the tabledefs in the front end, you have information that points you to the back end. This is in the FE tabledef's .connect property, which is a string. It tells you the device, path, name, and file type of the BE file that contains the referenced table. So what I do in my startup form is I prevent anyone from using the "bypass" methods. I run some Form_Open code to see if the device and path are the same for the FE file and the BE file. If they are the same then some schmuck is running the FE from the wrong location. That person gets a message box (OK-only style) that says "Don't do this. When you click OK, I will terminate your session. You need to copy the FE file to your local computer." Hint - the file name and type follow the last "/" character in the two strings. So find the pieces parts by reverse-parsing with InStrR (I think that's the correct function) to find the rightmost "/" and then do a Left$ from that location. That is the device and path isolated from the rest of the specification.

 

[CharlesWilliams]

Thanks Galaxiom, I will look into the Autoupdater. Also I don't have a table of users but willl look into that also. Do you have any examples of how to accomplish this?

- Charles

 

[boblarson]

Use AutoFEUpdater to distribute your FrontEnds.
http://autofeupdater.com/

And I have a free one as well. (see my signature)

 

[CharlesWilliams]

And I have a free one as well. (see my signature)

Thank You Bob. I downloaded it and will also check this one out.

 

[ChipperT]

I have a split database that is dispersed to disconnected users. I split it to make it easier to maintain the FE even though each user has both the FE and BE locally on their own computer. I know there are autoupdaters out there that make it easy to distribute new FEs for network users, but is there an easy way for me to do the same for disconnected users, just distributing the FE?