Welcome to SPN

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

Sign Up Now!

Split database with linked tables

Discussion in 'Information Technology' started by Janelle.Dunlap@ge.com, Jul 28, 2006.

  1. Janelle.Dunlap@ge.com

    Janelle.Dunlap@ge.com
    Expand Collapse
    Guest

    I have an Access database that I need to split into a front-end and
    back-end to allow multiple users. Currently my database is linked to
    an external Excel spreadsheet and it will not recognize this linked
    table when I go to split the database. Is there a workaround for this?
    Is it possible to split the database without any tables, add a linked
    table to the front-end that points to the spreadsheet, and then link
    this table to the back-end? Thanks in advance for any suggestions!
     
  2. Loading...

    Similar Threads Forum Date
    India Team Anna splits over politics Breaking News Sep 22, 2012
    India Split in Team Anna. Two core members quit committee. Breaking News Oct 18, 2011
    Canada Community Split on Resolution Banning Non-baptized Sikhs from Running Guru Nanak Temple Breaking News Jul 14, 2011
    India High Priests May Discuss Split Gurpurabs Next Week Breaking News Jan 7, 2011
    India Split in Badal Family, Amarinder Returns to Centrestage Breaking News Dec 30, 2010

  3. Jeff Boyce

    Jeff Boyce
    Expand Collapse
    Guest

    Why do you feel you need to link to both backend and frontend?

    Regards

    Jeff Boyce
    Microsoft Office/Access MVP

    <Janelle.Dunlap@ge.com> wrote in message
    news:1151361849.163377.106650@75g2000cwc.googlegroups.com...
    >I have an Access database that I need to split into a front-end and
    > back-end to allow multiple users. Currently my database is linked to
    > an external Excel spreadsheet and it will not recognize this linked
    > table when I go to split the database. Is there a workaround for this?
    > Is it possible to split the database without any tables, add a linked
    > table to the front-end that points to the spreadsheet, and then link
    > this table to the back-end? Thanks in advance for any suggestions!
    >
     
  4. gee664

    gee664
    Expand Collapse
    Guest

    You can remove the link to the xls, split the db, and then re-link to the xls
    from the front-end db.

    "Janelle.Dunlap@ge.com" wrote:

    > I have an Access database that I need to split into a front-end and
    > back-end to allow multiple users. Currently my database is linked to
    > an external Excel spreadsheet and it will not recognize this linked
    > table when I go to split the database. Is there a workaround for this?
    > Is it possible to split the database without any tables, add a linked
    > table to the front-end that points to the spreadsheet, and then link
    > this table to the back-end? Thanks in advance for any suggestions!
    >
    >
     
  5. Janelle.Dunlap@ge.com

    Janelle.Dunlap@ge.com
    Expand Collapse
    Guest

    I thought this was how a split database works - the BE and FE share
    linked tables. I could be wrong.

    Jeff Boyce wrote:
    > Why do you feel you need to link to both backend and frontend?
    >
    > Regards
    >
    > Jeff Boyce
    > Microsoft Office/Access MVP
    >
     
  6. Jeff Boyce

    Jeff Boyce
    Expand Collapse
    Guest

    A front-end can link to any number of back-ends. If some of your data is in
    an Access .mdb file, and some is in Excel, and some is in a DB2 database,
    and some is in ..., you can use a front-end and links to all these. You
    would NOT need to create links to any of these from within the back-end
    (remember, you could have several).

    Regards

    Jeff Boyce
    Microsoft Office/Access MVP

    <Janelle.Dunlap@ge.com> wrote in message
    news:1151418464.968431.314150@c74g2000cwc.googlegroups.com...
    >I thought this was how a split database works - the BE and FE share
    > linked tables. I could be wrong.
    >
    > Jeff Boyce wrote:
    >> Why do you feel you need to link to both backend and frontend?
    >>
    >> Regards
    >>
    >> Jeff Boyce
    >> Microsoft Office/Access MVP
    >>

    >
     
  7. Janelle.Dunlap@ge.com

    Janelle.Dunlap@ge.com
    Expand Collapse
    Guest

    Ok...this is making more sense to me but I am unclear on how I would
    physically split my database. Do I just do it manually by creating an
    empty database and then linking to my spreadsheet, which creates my
    back-end, which I point to my front-end containing my forms, coding,
    etc? If so, how do I go about pointing my front-end to the back-end
    without using the Database Splitter Tool. The reason I ask is that it
    currently won't let me use this tool to split my db beacuse it doesn't
    recognize that I have any tables in my db (I only have 1 linked table
    to excel). Hopefully I am making sense. I appreciate your help.




    Jeff Boyce wrote:
    > A front-end can link to any number of back-ends. If some of your data is in
    > an Access .mdb file, and some is in Excel, and some is in a DB2 database,
    > and some is in ..., you can use a front-end and links to all these. You
    > would NOT need to create links to any of these from within the back-end
    > (remember, you could have several).
    >
    > Regards
    >
    > Jeff Boyce
    > Microsoft Office/Access MVP
    >
     
  8. Janelle.Dunlap@ge.com

    Janelle.Dunlap@ge.com
    Expand Collapse
    Guest

    I think I figured out how to split manually....by making two copies of
    my db, deleting the table in one to create a FE and deleting the forms,
    coding, etc in the other to create a BE. Problem is when I go to the
    FE to link to the table in the BE it still is not recognizing the
    table, I believe because it is already linked to a spreadsheet. I am
    at a loss of what to do.
     
  9. Jeff Boyce

    Jeff Boyce
    Expand Collapse
    Guest

    I may be mis-reading, but it sounds like you are leaving a link to the
    spreadsheet in the back-end. You don't need to link to the spreadsheet from
    the back-end, only the front-end.

    Regards

    Jeff Boyce
    Microsoft Office/Access MVP

    <Janelle.Dunlap@ge.com> wrote in message
    news:1151428587.113961.25290@m73g2000cwd.googlegroups.com...
    >I think I figured out how to split manually....by making two copies of
    > my db, deleting the table in one to create a FE and deleting the forms,
    > coding, etc in the other to create a BE. Problem is when I go to the
    > FE to link to the table in the BE it still is not recognizing the
    > table, I believe because it is already linked to a spreadsheet. I am
    > at a loss of what to do.
    >
     
  10. Janelle.Dunlap@ge.com

    Janelle.Dunlap@ge.com
    Expand Collapse
    Guest

    You are not misreading, maybe I am still confused....I though the BE is
    supposed to contain all the data (or tables) while the FE contains only
    the application (forms, coding, etc.). I was thinking that I needed to
    link the spreadsheet to the BE and then link this table from the BE to
    the FE.



    Jeff Boyce wrote:
    > I may be mis-reading, but it sounds like you are leaving a link to the
    > spreadsheet in the back-end. You don't need to link to the spreadsheet from
    > the back-end, only the front-end.
    >
    > Regards
    >
    > Jeff Boyce
    > Microsoft Office/Access MVP
    >
     
  11. Ron2006

    Ron2006
    Expand Collapse
    Guest

    Think of it this way: You cannot link to a link.

    The idea of the FE is that no tables are local to it. And the FE can
    point to many sources of data - to many BE. In your case one of your
    BEs is an mdb and the other is a spreadsheet. FE-BE says that the FE
    contains no tables not that one BE contains all the data/tables.

    Physically each one of your tables could be in a different mdb. You
    would still have a FE-BE situation. Forms in the FE and all data in
    BEs. (In fact this is one way that you could get around the max 2G size
    for a mdb - spliting the tables amoung many mdbs.)

    You FE should simply point to whatever BE file contains the data.

    Ron
     
  12. Janelle.Dunlap@ge.com

    Janelle.Dunlap@ge.com
    Expand Collapse
    Guest

    Thanks for the reply, I think I understand now. My BE is actually my
    spreadsheet, and since I only have one table I guess this also means
    that my database is already split. Thanks for the clarification.




    Ron2006 wrote:
    > Think of it this way: You cannot link to a link.
    >
    > The idea of the FE is that no tables are local to it. And the FE can
    > point to many sources of data - to many BE. In your case one of your
    > BEs is an mdb and the other is a spreadsheet. FE-BE says that the FE
    > contains no tables not that one BE contains all the data/tables.
    >
    > Physically each one of your tables could be in a different mdb. You
    > would still have a FE-BE situation. Forms in the FE and all data in
    > BEs. (In fact this is one way that you could get around the max 2G size
    > for a mdb - spliting the tables amoung many mdbs.)
    >
    > You FE should simply point to whatever BE file contains the data.
    >
    > Ron
     
  13. Ron2006

    Ron2006
    Expand Collapse
    Guest

    That is great if your IT dept would let you use SQL. If they won't (and
    ours won't) our options are cut significantly.

    MDB is not ideal solution, but it sure beats trying to share
    spreadsheets.
     
  14. Ron2006

    Ron2006
    Expand Collapse
    Guest

    As to putting the large vs small tables in one or the other, it is
    rather a point of whether independent users are going to be changing
    the data in those small or large tables.

    Static tables are definitely items to consider keeping in the FE.

    But obviously non-static (dynamic - multiuser updatable) tables need to
    be in the BE.
     

Share This Page