database splitter

[dimpie]

I have developed a application in access. Now, i moved this to the a common
drive where all my tem members can access it.

I tried database splitter which splits into front end(forms, queries...)
and backend(tables). also, i can see all tables from the front end are linked
to the backend.

My questions:

when i install the front end as a shortcut to all the users, will this front
end point to the back end in the shared drive???. So i will have 10 copies of
the front end and 1 copy of the backend.

Is there a way down the line that i can unsplit the database???

Thank for all the help...

 

[Douglas J. Steele]

It's not simply a case of installing a shortcut: each user should have
his/her own copy of the front-end, ideally on his/her hard drive.

To ensure that the front ends all point to the correct back end, regardless
of how the users have their drives mapped, use a UNC
(\\server\share\folder\file.mdb) reterence rather than a mapped drive
(E:\folder\file.mdb). To do this through the Linked Table Manager, browse to
the database file through Network Neighborhood, rather than through the
mapped drive.

There should be no legitimate need to unsplit the database. However, if you
feel you have to, you can either delete the linked tables from a copy of the
front-end and import the tables into it, or you can open the back end and
import all of the objects from a copy of the front-end.

 

[John W. Vinson]

I have developed a application in access. Now, i moved this to the a common
drive where all my tem members can access it.

I tried database splitter which splits into front end(forms, queries...)
and backend(tables). also, i can see all tables from the front end are linked
to the backend.

See Tony's excellent summary of the issues concerning split applications at
http://www.granite.ab.ca/access/splitapp.htm

My questions:

when i install the front end as a shortcut to all the users, will this front
end point to the back end in the shared drive???. So i will have 10 copies of
the front end and 1 copy of the backend.

Correct. Each user should get *THEIR OWN COPY* of the frontend, not just a
shortcut to it though. If users all have the same drive mappings (i.e. if the
shared folder containing the backend is everyone's K: drive) you can use the
drive letter, but you may instead want to open the frontend; use Tools...
Database Utilities... Linked table Manager; select all the tables and check
the "Always ask for a new location" checkbox; and relink to the backend,
navigating via Network Neighborhood. This will store the path to the backend
in the \\Servername\path\database.mdb format which will be insensitive to
drive letter mapping variations.

Is there a way down the line that i can unsplit the database???

I can't think of any good reason to do so, but yes; you can open a copy of the
frontend, delete all the links to the tables, and use File... Get External
Data... Import to import the tables from the backend.

John W. Vinson [MVP]

 

[Tony Toews [MVP]]

I can't think of any good reason to do so, but yes; you can

Performance will suffer after splitting. However the benefits of
splitting far out weigh the problems. There is a link from the page
on my website that John Vinson mentions that covers the performance
answers.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/