>MS ACCESS97
>
>I have the following questions regarding preparing an mdb for distribution.
>
>1. What is the proper order for the following steps (and any I might have left out ) after creating an mdb:
>
>Create an mde
>Create Groups and Users and assign permissions
>Secure (mdb or mde ?)
>Split the Database
>
>2. Which files should go on the clients machine to give them the app. but not the source code? I have the following files:
>
>myapp.mdb
>myapp.mde
>securemyapp.mdb
>myapp.bmp (splash screen)
>myapp_be.mdb
>
>3. Why do I have to setup the Groups and Users and their permissions on each machine? Isn't there a way to do this once and have it carry through to each installation?
>
>TIA for any help
A partial attempt at answers:
1 & 2) AFAIK if you save as MDE you do not need to distribute the MDB. The MDB will be your original that only you need to have for development and maintenance. The MDE will not have any source or editable objects whatsoever. And the main reason for the backend db (myapp_be.mdb) is that on a multi-user deployment you put only one copy of this in a file server for everyone to access.
I am not too familiar with securing an access db other than protecting the source code, so here's a link that might be helpful on your other questions:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odeopg/html/deovrsecuringaccessdatabases.aspHTH
