Splitting DB

[Antonio]

Hello, all...I know that there is always a discussion
about splitting a db, but here are my questions:
1) Should I create an MDE file BEFORE I SPLIT?
2) After I split, do I work on a MDB file to make design
changes, then re-make an MDE and split again?
Antonio

 

[Antonio]

Also,

what about backup?

 

[Van T. Dinh]

The normal process is to split your database to Front-End and Back-End mdb
and then convert the Front-End to MDE format. There is no need to convert
the Back-End since the Back-End should only contain Tables, i.e. no
compiling of code required.

You MUST keep a copy of the Front-End in a safe & secure place since if you
want to modify the Access objects, you can only modify the MDB file (you
cannot modify the MDE file). Once you finish modifications, you need to
make new MDE Front-End and distribute the new MDE to users.

Provide you keep a copy of the Front-End MDB (and MDE), you then need to
have regular backups of the Back-End since the Back-End contains (users')
data.

--
HTH
Van T. Dinh
MVP (Access)

 

[sam1967]

The normal process is to split your database to Front-End and Back-End mdb
and then convert the Front-End to MDE format. There is no need to convert
the Back-End since the Back-End should only contain Tables, i.e. no
compiling of code required.

Why do you need to convert to an MDE ?

 

[Van T. Dinh]

Only if you don't want users / others to look at the
source code or modify the code since the Text component of
of the code is removed from the MDE file. The database
should, *in theory*, run a bit faster as the code has
already been compiled.

HTH
Van T. Dinh
MVP (Access)