Hi,
I want to split my Access DB and want the back-end to be in the same
directory as the front-end wherever I might move the db to. When I go into
the DB splitter it wants me to select a directory. Does this mean that the
back-end must remain in the selected directory? My db will be used by
various users and will be placed in whatever directory they want, so the
front-end must look for the back-end in the same directory. Is this possible?

Thanks,
--
Phil

If you want the BE to follow the FE, then it doesn't make sense to split the
database in this case.

To do what you want, you must put some code to relink the tables when
necessary. You will find many exemple on the internet on how to relink
tables; however, I don't know if this is a good idea in your case.

S. L.

"Phil" <(E-Mail Removed)> wrote in message
news:738E52AA-BA78-4586-8882-(E-Mail Removed)...
> Hi,
> I want to split my Access DB and want the back-end to be in the same
> directory as the front-end wherever I might move the db to. When I go
> into
> the DB splitter it wants me to select a directory. Does this mean that
> the
> back-end must remain in the selected directory? My db will be used by
> various users and will be placed in whatever directory they want, so the
> front-end must look for the back-end in the same directory. Is this
> possible?
>
> Thanks,
> --
> Phil

On Sun, 2 Jan 2005 19:49:01 -0800, "Phil"
<(E-Mail Removed)> wrote:

>Hi,
>I want to split my Access DB and want the back-end to be in the same
>directory as the front-end wherever I might move the db to. When I go into
>the DB splitter it wants me to select a directory. Does this mean that the
>back-end must remain in the selected directory? My db will be used by
>various users and will be placed in whatever directory they want, so the
>front-end must look for the back-end in the same directory. Is this possible?
>
>Thanks,

Typically in a split database each user has their own copy of the
frontend, but they all share the same backend: that's the main POINT,
allowing multiple users to share and update the same data over a
network. Do you really intend that each user have their own
independent set of data, with no connection?

If so, you may want to just distribute the unsplit database. The
alternative is to get some VBA code to automatically relink the
database (check to see if the backend is correctly linked and, if not,
look in the same folder as the frontend and relink). The _Access
Developer's Handbook_ has code for this, and there are several
examples on the web.

John W. Vinson[MVP]

"Phil" <(E-Mail Removed)> wrote in message
news:738E52AA-BA78-4586-8882-(E-Mail Removed)...
> Hi,
> I want to split my Access DB and want the back-end to be in the same
> directory as the front-end wherever I might move the db to. When I go
into
> the DB splitter it wants me to select a directory. Does this mean that
the
> back-end must remain in the selected directory? My db will be used by
> various users and will be placed in whatever directory they want, so the
> front-end must look for the back-end in the same directory. Is this
possible?

I have never used the splitter because it's so easy to just do it manually.
The process is simple:

1. Make 2 copies of your database
2. Delete the tables from 1 copy (Front-end)
3. Delete everything else from the other copy (Back-end)
4. Link the tables in the back-end to the front-end using:

File ... Get External Data ... Link

The back-end needs to reside on a server which all the other computers can
see. I can reside on a workstation, but is more stable if that workstation
is used as a server in a peer-to-peer network (workgroup) The linked
front-end needs to reside on each workstation. The only time when it makes
no difference if a database is split is when there is a single user. In all
other multi-user scenarious, the database should be split in order to reduce
the chances for corruption.

If you can map all the computers to the server using the same drive letters
you can maintain a single backup copy of the front-end on the server and
download it to any workstation. Failing that UNC (Universal Naming
Convention) is preferrable. If you must, separately mapping each front-end
to the server (data in the back-end) is preferrable to using an unsplit
database.
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads:
http://www.datastrat.com
http://www.mvps.org/access