Database split!!

[Switchwork]

Sorry I am here again. Just want to clarify a few things that I have found out!! Just to be on the safe side before I attempt to do this split. The problem I have come across is this. I use my computer which is the one that the two other computers are linked to and the database is in the shared folder. My collegues both use only a form in the database that is it!!! I am the main user of the database. I enter the remainding data the following day. I also have to produce the weekly reports (which are a breakdown of jobs done for each customer in the week) we attach this report to an invoice. So I need to have access not only to the tables but to forms and reports and the queries as I pull up the prices of the jobs as well when we need them. The thing is I have not designed a switchboard for my database as I was not sure how to go about doing this. So all the queries,forms, reports are used direct from the database window. Please could you help me with this. I really want to split the database but really need to have access to the whole lot. If there is a way of doing this please someone let me know as I am in dire straits here. We have not got a seperate server for our computer as I said the other two computers are connected to mine but we need all three to have the forms reports and stuff. I don't mind having the tables on mine as I understand all that it is my design after all. Is there a way of doing it so this can happen or do I have to do something totally different.

PLEASE PLEASE PLEASE PLEASE HELP ME!!! I am desperate to get this sorted so if you can help me with this I would be soooooooo happy........

 

[pono1]

Peer to peer scares me a little but it might be worth a try if you're desperate.

Are you sure you need a switchboard? Since your two other users only use 1 form, the easiest way to make this happen would be along these lines...

1. Create a new folder on your PC.
2. Share the folder, giving it a share name of, say, DB1.
3. Copy your Access database file to the new folder. (Warning: Keep the original file in a safe place during a test phase).
4. Go to another PC on your network and log on.
5. Use Net Neighborhood to find the Back-end PC (yours) and then the shared folder you just created (DB1) and then the Access file inside. Copy the file to the computer you're now sitting at.
6. Open the copied file (the file located on the PC where you're seated) and delete everything -- tables, queries, reports, forms -- except for the one form you need the user at this PC to use.
7. Click the File pulldown menu.
8. Click Get External Data.
9. Click Link Tables.
10. Browse to the back-end PC and find your file in the shared folder you just created and link to the tables inside.

That should do it...or at least get you close.

Regards,
Tim

 

[Pat Hartman]

What you need to do before using the db splitter wizard:
1. Make a backup of the database and copy it to a safe place

Using the splitter wizard does several things.
1. It creates a new db called a back end (be for short)
2. It copies all the tables to the new be db
3. It renames all the tables in the front end (fe for short) db
4. It links the tables from the be db to the front end db so that even though the old tables still exist, everything in the front end db will point to the linked tables.

What you need to do afterward:
1. Delete the old tables. They should have a suffix of _local. The linked tables will have black arrow icons so you can visually identify them.
2. Copy the fe to a safe place
3. Copy the fe to each user's workstation so that they have their own copy.
4. Move the fe from the shared directory to your private drive so that only the fe remains in the shared directory.

At this point, each user has their own copy of the fe and you have the master copy. All the copies are linked to the be on the shared drive. That means that no matter who updates data, everyone sees the changes.

Future development should be done on your private copy. When you are happy with the modifications, distribute new copies to the other users to replace their existing copies. The data is not affected since it is in a separate db on the shared drive.

When you are doing development, it is best not to work with the production data. You can copy the be from the server to your local drive and use the linked tables manager to point your copy of the fe to the local copy of the be. After you make your changes, don't forget to relink your fe to the shared be before you distribute the changed db.

Making a switchboard is pretty easy if you use the wizard. The wizard builds a form named Switchboard and a table named Switchboard Items. It is fine that this table stays in the fe. You just add items to the switchboard by making selections from the wizard screens. If you don't like what you created, you can open the switchboard manager and make changes. Or if you want to start from scratch, delete both the Switchboard form and Switchboard Items table. The wizard will recreate them when you run it again.

Once the switchboard is to your liking, set it as the start up form.