After splitting

[accessuser via AccessMonster.com]

hi,

After database splitting, would I be able to add more forms in the future?
Thanks!

 

[Rick Brandt]

hi,

After database splitting, would I be able to add more forms in the future?
Thanks!

Certainly. Splitting (by itself) changes nothing about what further changes you
can make to either of the resulting files.

 

[fredg]

hi,

After database splitting, would I be able to add more forms in the future?
Thanks!

Yes!

 

[accessuser via AccessMonster.com]

Sorry i should have specified more information. I am thinking of making a
MDE (the one that nobody can use the design view and change the design) and
then split the MDE. From there, would I be able to add more forms in future?

thanks!

 

[Rick Brandt]

Sorry i should have specified more information. I am thinking of making a
MDE (the one that nobody can use the design view and change the design) and
then split the MDE. From there, would I be able to add more forms in future?

No you cannot add forms to an MDE.

One of the main advantages to splitting is that there can be multiple front
ends. One of these is the MDB that you keep so you can continue to make
development changes. Then you use that to make a new MDE which you distribute
to your users.

 

[accessuser via AccessMonster.com]

Do you mean by split the Main database first into front and back end, and
then split the front end into MDE? How would the information carry over? So
in this way, I will be doing 2 database splits, is it right?

 

[Rick Brandt]

Do you mean by split the Main database first into front and back end, and
then split the front end into MDE? How would the information carry over? So
in this way, I will be doing 2 database splits, is it right?

No. When you split you will have two MDBs. One with just tables and one with
everything else. When you are ready to deploy the app to users you use the MDB
containing forms, reports, code, etc., and you create an MDE from it. Now you
have three files, a back end MDB, a front end MDB and a front end MDE. You give
each user a copy of the MDE and you keep the front end MDB for further
development work.

While users are happily using the MDE you gave them you can continue to make
development changes to the front end MDB (new forms, reports, etc.). When you
have a new "version" to deploy you make a new MDE and send copies of that to
your users. Since the data is all stored in the back end MDB none of this makes
any difference to the data at all. Your users simply replace one MDE with a new
one and off they go.

 

[accessuser via AccessMonster.com]

Thank you so much for your detail explaining!!!!

No. When you split you will have two MDBs. One with just tables and one with
everything else. When you are ready to deploy the app to users you use the MDB
containing forms, reports, code, etc., and you create an MDE from it. Now you
have three files, a back end MDB, a front end MDB and a front end MDE. You give
each user a copy of the MDE and you keep the front end MDB for further
development work.

While users are happily using the MDE you gave them you can continue to make
development changes to the front end MDB (new forms, reports, etc.). When you
have a new "version" to deploy you make a new MDE and send copies of that to
your users. Since the data is all stored in the back end MDB none of this makes
any difference to the data at all. Your users simply replace one MDE with a new
one and off they go.

 

[David W. Fenton]

Do you mean by split the Main database first into front and back
end, and then split the front end into MDE? How would the
information carry over? So in this way, I will be doing 2
database splits, is it right?

Have you read the help file's definition of what an MDE is? It would
seem from your questions that you've omitted that basic and obvious
step.