Is it possible to UNSPLIT a mdb

[Bob Richardson]

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?

 

[Douglas J. Steele]

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

Why, though?

 

['69 Camaro]

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]

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.

 

[aaron.kempf]

i would reccomend using ac ACCESS DATA PROJECT instead of splitting
into frontend-backend

 

[Dirk Goldgar]

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.

 

[Douglas J Steele]

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.

 

['69 Camaro]

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]

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.

 

[aaron.kempf]

of course; if you use ADP; you dont have to deal with split, link, dsn,
refresh

none of that crap

you dont have to write code to update sql-passthroughs

you can consume sprocs with parameters quite well

i mean-- there is a better way; instead of dealing with all the MDB
bullshit

 

[Gary]

Aaron are you married to ADP?

I think you must be in love? ...

 

[aaron.kempf]

yeah i am.

im just sick and tired of dealing with MDB; and i was **ENLIGHTENED** 5
years ago.. when i was working on some large apps and i had too many
columns for a silly little MDB.

I just knwo that 50% of the crap that you guys do is much easier to do
with sprocs and views.. i mean.. real parameters?

it ROCKS compared to silly mdb