How to split a access 2003 database - the whole nine yards

[chemexchange]

Hi,

I'm a systems/network admin that has very little experience with Access. I
have mulitple users that need to access an Access database at the same time.
While searching I came across "splitting the database". After researching
the topic, it sounded exactly like what I wanted. So, I printed out a couple
of articles from Microsoft and from a couple of fourums I found and figured I
had enough info to get the job done.

I connected to the database from my home computer to a network share at work
via a VPN. That is I opened up Access 2003 and open the database (let's call
it test). I make a backup of the original database (only about 4MB) and
proceed to split the database. Everything worked perfectly! The database
wizard asked for the original database and then made the backend,
test_be.mdb. Both are in the same shared network folder (lets call the
folder "database"). Now I have two files in the network shared database
folder. These files are test.mdb and test_be.mdb. Now I know the
test_be.mdb is the new backend to the database, but that is where I'm stuck.
What do you do next? How/where is the front end that every article keeps
talking about? I need someone to explain to me the "whole nine yards" of
splitting a database and getting the end users setup to access the split
database.

I found a couple of articles that referenced access developers toolkit to
make the frontend, but what is that and where do you get it. Or do I even
need that. I have a total of about 10 users spread across two cities that
need to access the test database. All of the end users have a copy of Access
2003 SP2 installed on their machines.

Thanks

Complete Access Newbie

 

[Albert D. Kallal]

I explain about splitting here:

http://www.members.shaw.ca/AlbertKallal/Articles/split/index.htm

And, about usign a vpn, or lan/wan here:

http://www.members.shaw.ca/AlbertKallal//Wan/Wans.html

Read both of the above...and you should be up to speed....

 

[Tom Wickerath]

Hi chemexchange,

Your front-end (FE) database *is* test.mdb. If you open this database and
view the Tables tab, you should see little black arrows pointing to each
table. These are linked tables (essentially shortcuts to the shared tables in
the BE database, test_be.mdb). Each user should run their own copy of the FE
database, test.mdb.

In addition to the information that Albert has provided, take a look a my
article:

Implementing a Successful Multiuser Access/JET Application
http://www.access.qbuilt.com/html/multiuser_applications.html

This article covers the essentials of a successful multiuser JET
application, run over a LAN. Since you have users in different cities, you
will need to take additional steps to deal with a WAN. Using Terminal Server
is a viable option. Each users FE is installed in their working folder on the
Terminal Server (at least that is my understanding of how it works).


Tom Wickerath
Microsoft Access MVP

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________

 

[chemexchange]

Thanks so much. This really helps me out. I'm going to check out your
article in a few minutes. I'm sure I'll learn even more from the article.
My main problem was finding the frontend and it was right there in front of
me the whole time. I just figured the original file couldn't be the fe
becuase it was the exact same size as before I split it. I just assummed it
would be slightly smaller once it was split. But anyway, thanks for all the
help. I'm set now.

 

[chemexchange]

Thanks a lot, Albert. The article really helped clear up some issues I was
having. I didn't realize the frontend of the database was in front of me the
whole time. I just figured the original file couldn't be the fe becuase it
was the exact same size as before I split it. I just assummed it would be
slightly smaller once it was split. But anyway, thanks for all the help.
I'm set now.

 

[John Vinson]

I just figured the original file couldn't be the fe becuase it
was the exact same size as before I split it.

Access doesn't "clean up" after itself. If you use Tools... Database
Utilities... Compact and Repair you'll recover the space formerly
occupied by the tables, but not until then.

John W. Vinson[MVP]