How to recombine a split database?

[James Ivey]

Access Newbie using Access 2007

I created a real simple database about a year ago in Access2003, and split
it into front end and back end. Now I would like to recombine it into one
file.

How does one do that in Access2007?

James

 

[Allen Browne]

Open the back end.

On the Database Tools tab of the ribbon, import from Access.

Choose the front end file.

Import all the queries, forms, reports, etc., and be sure to click the
advanced options if you need to import custom toolbars or import/output
specs.

Then open the code window, and choose References on the Tools menu. Make
sure the same references are chosen as you had in your front end. And
Compile (Debug menu in the code window.)

It's quite a simple process.

 

[James Ivey]

Worked like a charm, Allen. Thanks a bunch.

James

 

[Tony Toews [MVP]]

I created a real simple database about a year ago in Access2003, and split
it into front end and back end. Now I would like to recombine it into one
file.

Why would you want to do such? We strongly urge folks to use split
databases.

tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[David W. Fenton]

I created a real simple database about a year ago in Access2003,
and split it into front end and back end. Now I would like to
recombine it into one file.

Don't.

 

[Ahmed]

Access Newbie using Access 2007

I created a real simple database about a year ago in Access2003, and split
it into front end and back end. Now I would like to recombine it into one
file.

How does one do that in Access2007?

James
Any1 found a solution for this?

 

[James Ivey]

Hi Tony,

Well, it just seems like it would be easier to manage right now in the
"start-up" phase.

The person who is doing the data entry, and is actually going to use the
database is several states away, so it seems easier to email the single
file, rather than get her to deal with the front-end file properly.

Our database is not very big - as one file its a little over 800 Kb. So
emailing it back and forth isn't an issue. When I had it split, the
front-end file was 700 Kb, even after a compact.

Why do you "strongly urge" people split?

James

 

[James Ivey]

Why?

Don't.

 

[Allen Browne]

James, if you plan to deploy the database to other places, I would
definately leave it split as Tony and David suggested.

Say they want an extra report. If it's split, you can add the report, and
send out the new front end *without* overwriting their existing data.

 

[David W. Fenton]

Why?

Every Access application with more than one user should be split. NO
EXCEPTIONS.

Every Access application where the user needs to get updates to the
forms/reports from someone else should be split, even if it has only
one user. NO EXCEPTIONS.

Every replicated Access app should be split. NO EXCEPTIONS.

And every user should have an individual copy of the front end, no
matter whether the app is running on a workstation or in a Terminal
Server/Citrix session. NO EXCEPTIONS.