FE/BE question

[Slez via AccessMonster.com]

I'm currently making some modifications to a copy of a database that is not
split. The mods are to both forms/reports, as well as tables. After I
finish the modifications, I intend to try splitting the database so there is
a FE/BE structure. Because users are still using the original database, data
in the tables has changed, so at some point, I will need to ask everyone to
stay out of the original so I can make the table structure updates without
losing any data.

In my mind, a split database is really nothing more than my Front End (being
all the forms and reports) with linked tables (which is the Back End). So if
I get rid of the tables in my modified database, then make the table mods in
the original database, and finally use the "File - Get External Data - Link
Tables" feature in the modified one to link the tables from the original one,
that in turn creates my split database.

My question is this: Is my thinking correct on this? Does that in fact
create a "split database"?

Having never done this before, I guess I wanted to make sure I was looking at
this in the right frame of mind. I appreciate any opinion!

 

[Ruel Cespedes via AccessMonster.com]

Allow me to give you some advise.

FrontEnd = Queries, Forms, Reports, Pages, Macro's, and Modules
BackEnd = Tables and Relationships

Steps to Follow:

Step 1. Get Everyone out of the .mdb file.
Step 2. Establish a common drive location for the BackEnd.
Step 3. Establish All Linked and Native Tables (Linked=All in BackEnd ::
Native=Local in FrontEnd).
Step 4. Backup the .mdb file as a Master Original.
Step 5. Split the .mdb file.
Step 6. Convert the FrontEnd to .mde (for Security of your code)
Step 7. Distribute the New .mde file.