Same result.
Personally, I prefer to split manually as you describe, because I can leave
some tables in the front end (e.g. user temp and config), and because
getting Access to rebuild things is useful at that stage of the process to
help avoid corruption after constantly changing things.
Or perhaps it's because I have been splitting since before there ever was a
splitter wizard. :-)
--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users -
http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
<Ca************@HeartOfDarkness.com> wrote in message
news:42658128.675421@news-server...
Is there any difference between splitting the .mdb vs. linking a table
in another .mdb file ? For example, if I use the database splitter
tool I end up with Widgets.mdb and Widgets_be.mdb. All the tables are
located in Widgets_be.mdb. However, let us say that I create a file
called Widgets2.mdb, move all the tables from Widgets.mdb into it, and
then link the tables from Widgets.mdb to Widgets2.mdb. Is there any
difference in how Access treats the files? Thanks for your help.