Welcome to SPN

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

Sign Up Now!

Is it possible to UNSPLIT a mdb

Discussion in 'Information Technology' started by Bob Richardson, Oct 27, 2005.

  1. Bob Richardson

    Bob Richardson
    Expand Collapse
    Guest

    My DB was split into a front end and back end DB. It works fine that way but
    I'd like to revert back to the original status. How can I put it back to a
    single mdb file?
     
  2. Loading...

    Similar Threads Forum Date
    Movies Ashdoc's movie review---Mission impossible 5 Rogue nation Theatre, Movies & Cinema Aug 12, 2015
    India Professor Bhullar's release possible after landmark SC judgement Breaking News Jan 21, 2014
    USA UPDATED! Dr. Prabjot Singh, Sikh Professor Attacked in Possible Hate Crime (2 Videos) Breaking News Sep 23, 2013
    A Shabad I came across - possible interpretations Sikh Sikhi Sikhism Aug 28, 2013
    To know God is to Love him, why this is not possible Sikh Sikhi Sikhism Mar 31, 2012

  3. Douglas J. Steele

    Douglas J. Steele
    Expand Collapse
    Guest

    Simply delete all of the linked tables, and import them into your database.

    Why, though?

    --
    Doug Steele, Microsoft Access MVP
    http://I.Am/DougSteele
    (no e-mails, please!)



    "Bob Richardson" <bobr at whidbey dot com> wrote in message
    news:1cudnVCYtbotbMLenZ2dnUVZ_s6dnZ2d@whidbeytel.com...
    > My DB was split into a front end and back end DB. It works fine that way
    > but I'd like to revert back to the original status. How can I put it back
    > to a single mdb file?
    >
     
  4. '69 Camaro

    '69 Camaro
    Expand Collapse
    Guest

    Hi, Bob.

    Delete the links in the front end, then import the tables from the back end
    into the front end. Reestablish all relationships in the front end that
    were previously in the back end.

    HTH.
    Gunny

    See http://www.QBuilt.com for all your database needs.
    See http://www.Access.QBuilt.com for Microsoft Access tips.


    "Bob Richardson" <bobr at whidbey dot com> wrote in message
    news:1cudnVCYtbotbMLenZ2dnUVZ_s6dnZ2d@whidbeytel.com...
    > My DB was split into a front end and back end DB. It works fine that way
    > but I'd like to revert back to the original status. How can I put it back
    > to a single mdb file?
    >
     
  5. Bob Richardson

    Bob Richardson
    Expand Collapse
    Guest

    I'm going through a major structural change to the DB and think it might be
    easier to keep everything in one place, rather than switching back and forth
    between two DBs.


    "Douglas J. Steele" <NOSPAM_djsteele@NOSPAM_canada.com> wrote in message
    news:uSXfaKn2FHA.1980@TK2MSFTNGP15.phx.gbl...
    > Simply delete all of the linked tables, and import them into your
    > database.
    >
    > Why, though?
    >
    > --
    > Doug Steele, Microsoft Access MVP
    > http://I.Am/DougSteele
    > (no e-mails, please!)
    >
    >
    >
    > "Bob Richardson" <bobr at whidbey dot com> wrote in message
    > news:1cudnVCYtbotbMLenZ2dnUVZ_s6dnZ2d@whidbeytel.com...
    >> My DB was split into a front end and back end DB. It works fine that way
    >> but I'd like to revert back to the original status. How can I put it back
    >> to a single mdb file?
    >>

    >
    >
     
  6. Dirk Goldgar

    Dirk Goldgar
    Expand Collapse
    Guest

    "'69 Camaro" <ForwardZERO_SPAM.To.69Camaro@Spameater.orgZERO_SPAM>
    wrote in message news:OFwr6Ln2FHA.2292@tk2msftngp13.phx.gbl
    > Hi, Bob.
    >
    > Delete the links in the front end, then import the tables from the
    > back end into the front end. Reestablish all relationships in the
    > front end that were previously in the back end.


    Normally, the relationships would be imported along with the tables,
    wouldn't they? I believe that's the default option.

    --
    Dirk Goldgar, MS Access MVP
    www.datagnostics.com

    (please reply to the newsgroup)
     
  7. Douglas J Steele

    Douglas J Steele
    Expand Collapse
    Guest

    Shouldn't make any difference. Worst case is you have to relink after making
    major changes in the backend, but even that's not normally required. I often
    split my applications before I start development.

    --
    Doug Steele, Microsoft Access MVP
    http://I.Am/DougSteele
    (no e-mails, please!)


    "Bob Richardson" <bobr at whidbey dot com> wrote in message
    news:RJadncpuftoonf3eRVn-oA@whidbeytel.com...
    > I'm going through a major structural change to the DB and think it might

    be
    > easier to keep everything in one place, rather than switching back and

    forth
    > between two DBs.
    >
    >
    > "Douglas J. Steele" <NOSPAM_djsteele@NOSPAM_canada.com> wrote in message
    > news:uSXfaKn2FHA.1980@TK2MSFTNGP15.phx.gbl...
    > > Simply delete all of the linked tables, and import them into your
    > > database.
    > >
    > > Why, though?
    > >
    > > --
    > > Doug Steele, Microsoft Access MVP
    > > http://I.Am/DougSteele
    > > (no e-mails, please!)
    > >
    > >
    > >
    > > "Bob Richardson" <bobr at whidbey dot com> wrote in message
    > > news:1cudnVCYtbotbMLenZ2dnUVZ_s6dnZ2d@whidbeytel.com...
    > >> My DB was split into a front end and back end DB. It works fine that

    way
    > >> but I'd like to revert back to the original status. How can I put it

    back
    > >> to a single mdb file?
    > >>

    > >
    > >

    >
    >
     
  8. '69 Camaro

    '69 Camaro
    Expand Collapse
    Guest

    Yup! Thanks for pointing that out. I forget that not everybody else does
    what I do. I normally leave what's already working alone while I press a
    button to import the objects without the relationships into a new database
    file to make the modifications, which then copies the Relationships Window
    layout and list of References to the new database, then compiles the code.
    Gets rid of any excess baggage and gives me a brand new set of system tables
    to work with. And I don't have to mess with the Relationships Window layout
    that ordinarily gets scrambled when it's imported.

    Gunny

    See http://www.QBuilt.com for all your database needs.
    See http://www.Access.QBuilt.com for Microsoft Access tips.


    "Dirk Goldgar" <dg@NOdataSPAMgnostics.com> wrote in message
    news:OalTsmr2FHA.1700@tk2msftngp13.phx.gbl...
    > "'69 Camaro" <ForwardZERO_SPAM.To.69Camaro@Spameater.orgZERO_SPAM>
    > wrote in message news:OFwr6Ln2FHA.2292@tk2msftngp13.phx.gbl
    >> Hi, Bob.
    >>
    >> Delete the links in the front end, then import the tables from the
    >> back end into the front end. Reestablish all relationships in the
    >> front end that were previously in the back end.

    >
    > Normally, the relationships would be imported along with the tables,
    > wouldn't they? I believe that's the default option.
    >
    > --
    > Dirk Goldgar, MS Access MVP
    > www.datagnostics.com
    >
    > (please reply to the newsgroup)
    >
    >
     
  9. Dirk Goldgar

    Dirk Goldgar
    Expand Collapse
    Guest

    "'69 Camaro" <ForwardZERO_SPAM.To.69Camaro@Spameater.orgZERO_SPAM>
    wrote in message news:uzSNi3u2FHA.3788@tk2msftngp13.phx.gbl
    > Yup! Thanks for pointing that out. I forget that not everybody else
    > does what I do. I normally leave what's already working alone while
    > I press a button to import the objects without the relationships into
    > a new database file to make the modifications, which then copies the
    > Relationships Window layout and list of References to the new
    > database, then compiles the code. Gets rid of any excess baggage and
    > gives me a brand new set of system tables to work with. And I don't
    > have to mess with the Relationships Window layout that ordinarily
    > gets scrambled when it's imported.


    Makes sense.

    --
    Dirk Goldgar, MS Access MVP
    www.datagnostics.com

    (please reply to the newsgroup)
     
  10. Gary

    Gary
    Expand Collapse
    Guest

    Aaron are you married to ADP?

    I think you must be in love? ...
     

Share This Page