Un-Split

[Michael Conroy]

I have an executive in Chicago who wants to see this database I have created
for the group in NYC. Currently, he does not have access to the "S" drive
where the split tables are located. And, for obvious reasons, I am not sure I
want him to have access to the real data. Is there a way to un-split the
database back into one big file so I can send that to him? Is it as simple as
importing the tables back into a copy of the front end file? Yet if I import
the files, won't that remove them from the back end on the network share? I
think I need some sort of copy and paste for tables. Your help, as always, is
greatly appreciated.

 

[John Spencer]

If you import the tables you are copying them - not moving them.

When you do import, your imported tables will have a suffix added to
them so they won't replace the links to the tables. You will have to
manually remove the suffix. When you do you will get a message that
this will replace the linked table by the same name.

The other option is to remove all the linked tables (you are really
removing the link, the tables will still exist) and then import all the
tables from the backend.

If you are unsure of doing this. Make a backup first so if something
happens that you don't like you can use the backups.

'====================================================
John Spencer
Access MVP 2002-2005, 2007
Center for Health Program Development and Management
University of Maryland Baltimore County
'====================================================

 

[Chris Mills]

If you want someone to see a COPY of the database, why not just send them a
copy of BOTH files, the Front-End and the Back-End? Thereafter, to update
them, you only need send another Back-End?

Why bother putting it into 1 file, vs 2 files, with all the attendant testing
that would involve?

However, to answer your question as originally posed, and excepting there may
be security settings to setup if you use Access Security, it's as simple as
deleting table-links first, and then importing the tables!

If you do it in this order, the newly-local tables will have the same names
and behaviour as the original linked tables. There can be coding problems
going from local-to-linked tables, but never from linked-to-local. Or so I
think <g>

I would not even think of generating a whole new tailorised file. Just use
what you already have and tested! If necessary, re-link the links to a local
Back-End on a drive C folder, where you will instruct him to install in the
same foldername on driveC.

Chris

P.S. Imports are copies not affecting the original data. But if you're unsure
what you're doing, that's why you take backups of everything! For this
purpose, backup files in the same folder would do! Windows Explorer, highlight
a file, <ctrl C> <ctrl V> voila copy of file!