Welcome to SPN

Register and Join the most happening forum of Sikh community & intellectuals from around the world.

Sign Up Now!

Splitting an Access Database

Discussion in 'Information Technology' started by Lateral, Jul 28, 2006.

  1. Lateral

    Lateral
    Expand Collapse
    Guest

    Hi Guys,

    I am playing around with "splitting" an Access database and it works fine.

    I have a question....when you split the database, you are asked to specify a
    folder that the database containing the tables is to reside. For example, if
    I specifiy c:\tables then the Splitting utility will place the database in
    this folder.

    If I then double click my original database it will use the tables located
    in the c:\tables folder...so far so good.

    My question is this, where is this path/folder information stored and can I
    change it so that once I split a database I can then "maually" and easily
    change the name of the path/folder containing the tables?

    Thanks for any help you can provide.

    Regards
    Greg
     
  2. Loading...


  3. RoyVidar

    RoyVidar
    Expand Collapse
    Guest

    > Hi Guys,
    >
    > I am playing around with "splitting" an Access database and it works
    > fine.
    >
    > I have a question....when you split the database, you are asked to
    > specify a folder that the database containing the tables is to
    > reside. For example, if I specifiy c:\tables then the Splitting
    > utility will place the database in this folder.
    >
    > If I then double click my original database it will use the tables
    > located in the c:\tables folder...so far so good.
    >
    > My question is this, where is this path/folder information stored and
    > can I change it so that once I split a database I can then "maually"
    > and easily change the name of the path/folder containing the tables?
    >
    > Thanks for any help you can provide.
    >
    > Regards
    > Greg


    In the Tools menu, Database Utilities, you'll find the Linked Table
    Manager.

    You can also play with it in code, for instance using the .Connect
    property of the DAO tabledef object.

    --
    Roy-Vidar
     
  4. Lateral

    Lateral
    Expand Collapse
    Guest

    Thanks Roy

    If I split the database and put the tables into a folder called c:\tables
    and then load the databases onto another PC that has only the Access runtime
    and want to move the tables database onto a network drive (eg: g:\tables),
    how can I do this?

    Thanks Greg

    "RoyVidar" wrote:

    > > Hi Guys,
    > >
    > > I am playing around with "splitting" an Access database and it works
    > > fine.
    > >
    > > I have a question....when you split the database, you are asked to
    > > specify a folder that the database containing the tables is to
    > > reside. For example, if I specifiy c:\tables then the Splitting
    > > utility will place the database in this folder.
    > >
    > > If I then double click my original database it will use the tables
    > > located in the c:\tables folder...so far so good.
    > >
    > > My question is this, where is this path/folder information stored and
    > > can I change it so that once I split a database I can then "maually"
    > > and easily change the name of the path/folder containing the tables?
    > >
    > > Thanks for any help you can provide.
    > >
    > > Regards
    > > Greg

    >
    > In the Tools menu, Database Utilities, you'll find the Linked Table
    > Manager.
    >
    > You can also play with it in code, for instance using the .Connect
    > property of the DAO tabledef object.
    >
    > --
    > Roy-Vidar
    >
    >
    >
     
  5. Joan Wild

    Joan Wild
    Expand Collapse
    Guest

    Copy the tables onto the server. Use linked table manager to refresh the
    links. Then distribute the frontend to the other computers (the link is
    stored in the frontend).

    --
    Joan Wild
    Microsoft Access MVP

    Lateral wrote:
    > Thanks Roy
    >
    > If I split the database and put the tables into a folder called
    > c:\tables and then load the databases onto another PC that has only
    > the Access runtime and want to move the tables database onto a
    > network drive (eg: g:\tables), how can I do this?
    >
    > Thanks Greg
    >
    > "RoyVidar" wrote:
    >
    >>> Hi Guys,
    >>>
    >>> I am playing around with "splitting" an Access database and it works
    >>> fine.
    >>>
    >>> I have a question....when you split the database, you are asked to
    >>> specify a folder that the database containing the tables is to
    >>> reside. For example, if I specifiy c:\tables then the Splitting
    >>> utility will place the database in this folder.
    >>>
    >>> If I then double click my original database it will use the tables
    >>> located in the c:\tables folder...so far so good.
    >>>
    >>> My question is this, where is this path/folder information stored
    >>> and can I change it so that once I split a database I can then
    >>> "maually" and easily change the name of the path/folder containing
    >>> the tables?
    >>>
    >>> Thanks for any help you can provide.
    >>>
    >>> Regards
    >>> Greg

    >>
    >> In the Tools menu, Database Utilities, you'll find the Linked Table
    >> Manager.
    >>
    >> You can also play with it in code, for instance using the .Connect
    >> property of the DAO tabledef object.
    >>
    >> --
    >> Roy-Vidar
     
  6. Albert D.Kallal

    Albert D.Kallal
    Expand Collapse
    Guest

    > If I split the database and put the tables into a folder called c:\tables
    > and then load the databases onto another PC that has only the Access
    > runtime
    > and want to move the tables database onto a network drive (eg: g:\tables),
    > how can I do this?


    Since you as a developer had to ask about the linked table manger, we can't
    possibility expect users to be trained on how to use/find this utility.

    So, most of us roll our own re-linking code. The code checks for the back
    end..and if not, then we pop up the file browse dialog, and have the user
    select a back end..and then re-link. this is a FAR FAR more user friendly
    approach then teaching users about the linked table manger.

    Further, in the runtime, we don't have the linked table manger anyway.
    However, as a ms-access developer, you will likely figure out LONG LONG
    before you deploy a runtime application that you need to roll your own
    re-linking code.

    So, build your own re-link code. It solves the issue of having to teach
    users about using the linked table manager, and it FURTHER solves issues
    since with the runtime you don't have the linked table manager. So, by
    building your own, you solve several problems at at once.

    The code to re-link tables can be found here:

    http://www.mvps.org/access/tables/tbl0009.htm

    And, the code to popup the file browse dialog can be found here:
    http://www.mvps.org/access/api/api0001.htm

    So, between the two above routines, in a short time you can cobble together
    some code that can re-link for you.

    So, the end result of your efforts is

    * It is more user friendly

    * Users can relink tables even with the runtime

    * You code now will check for tables in the back end, and ask to
    re-link...again saving valuable support calls/dollars.

    To check for the back end...just open any table, and trap the error....

    You can also use the dir command to check for the existence of the back end
    (I prefer this approach over that of testing/trapping an attempt to open a
    table).


    --
    Albert D. Kallal (Access MVP)
    Edmonton, Alberta Canada
    pleaseNOOSpamKallal@msn.com
    http://www.members.shaw.ca/AlbertKallal
     
  7. Lateral

    Lateral
    Expand Collapse
    Guest

    Thanks Albert

    Regards
    Greg

    "Albert D.Kallal" wrote:

    > > If I split the database and put the tables into a folder called c:\tables
    > > and then load the databases onto another PC that has only the Access
    > > runtime
    > > and want to move the tables database onto a network drive (eg: g:\tables),
    > > how can I do this?

    >
    > Since you as a developer had to ask about the linked table manger, we can't
    > possibility expect users to be trained on how to use/find this utility.
    >
    > So, most of us roll our own re-linking code. The code checks for the back
    > end..and if not, then we pop up the file browse dialog, and have the user
    > select a back end..and then re-link. this is a FAR FAR more user friendly
    > approach then teaching users about the linked table manger.
    >
    > Further, in the runtime, we don't have the linked table manger anyway.
    > However, as a ms-access developer, you will likely figure out LONG LONG
    > before you deploy a runtime application that you need to roll your own
    > re-linking code.
    >
    > So, build your own re-link code. It solves the issue of having to teach
    > users about using the linked table manager, and it FURTHER solves issues
    > since with the runtime you don't have the linked table manager. So, by
    > building your own, you solve several problems at at once.
    >
    > The code to re-link tables can be found here:
    >
    > http://www.mvps.org/access/tables/tbl0009.htm
    >
    > And, the code to popup the file browse dialog can be found here:
    > http://www.mvps.org/access/api/api0001.htm
    >
    > So, between the two above routines, in a short time you can cobble together
    > some code that can re-link for you.
    >
    > So, the end result of your efforts is
    >
    > * It is more user friendly
    >
    > * Users can relink tables even with the runtime
    >
    > * You code now will check for tables in the back end, and ask to
    > re-link...again saving valuable support calls/dollars.
    >
    > To check for the back end...just open any table, and trap the error....
    >
    > You can also use the dir command to check for the existence of the back end
    > (I prefer this approach over that of testing/trapping an attempt to open a
    > table).
    >
    >
    > --
    > Albert D. Kallal (Access MVP)
    > Edmonton, Alberta Canada
    > pleaseNOOSpamKallal@msn.com
    > http://www.members.shaw.ca/AlbertKallal
    >
    >
    >
     

Share This Page