Split Database Primer 1

[iamchemist]

Is there some resource that would help a newbie to Split Databases learn some of the cardinal rules, like "Don't Do This" or "Always Modify a Table In The Part That Contains The Tables - Not Links To The Tables", etc.

 

[MajP]

I am sure there is something on the web, but it is very simple
1) create two brand new databases
2) Use a naming convention so you know which is front end and back
Backend gets just the tables. Front end gets a link to those tables and all other forms, reports, queries and code.
3) Open the backend and use the import external data feature to import in all the tables. (you are done with the backend)
4) Open the front and use the import external data feature but this time choose link to the backend tables. If you did that correct the tables showing in the front end should have little arrow icons showing that they are links.
5) Make sure to do 4 first. Now do step 4 again but this time import all the other queries, forms, reports and code.
You are done

You can only modify tables in the backend, not possible from the front end.
6) If you move the backend, rename it, change folder location you will have to relink that backend tables.

 

[iamchemist]

MajP.

Thanks much for your reply! I'm not sure that I followed all of your guidelines, when I tried splitting my database the first time. I'll go back and try again.
By the way, does it make any difference whether the database application was written with splitting in mind? I'm sure the database in my case was NOT written with splitting in mind.

 

[MajP]

Any Access database can be split, there is no design ahead of time. You are just putting the tables by themselves into a separate database. Even if you are not splitting a database it is often useful to create a blank new database so it is nice and clean. Then use the import external data feature to import your objects into a clean database. A lot of crap can build up in the background so this is a way to clean it up.

 

[missinglinq]

Here's one:

Microsoft Access Split Database Architecture to Support Multiuser Environments, Improve Performance, and Simplify Maintainability

Linq ;0)>

Hope this helps!

There's always more than one way to skin a cat!

All posts/responses based on Access 2003/2007