Re: Best way to distribute an Access Database
- From: jptpjs <jptpjs@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 4 Oct 2005 16:36:02 -0700
I have a few thoughts, please comment where needed.
Things to consider when distributing an Access database to customer base and
be able to provide some updates to the program
Split into FE and BE
MDE the FE for code security
Is it necessary to password protect the BE?
Use developer edition to distribute Access Runtime files.
Is just diabling the startup good enough?
If installing FE and BE is the linking done automatically. Really just
creating FE and BE so I can make updates.
I assume these two can just be installed in a default directory.
What if installed in another directory, or moved will links work?
Install additional dlls for other controls such a date time picker.
Does the Access Runtime files conflict with installed versions of Access.
Thanks for your help
"Douglas J. Steele" wrote:
> That the normal approach taken.
>
> --
> Doug Steele, Microsoft Access MVP
> http://I.Am/DougSteele
> (no e-mails, please!)
>
>
>
> "jptpjs" <jptpjs@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:CB3961BB-B293-441E-A208-72FE456437F2@xxxxxxxxxxxxxxxx
> > Thanks,
> >
> > Would it make sense to create an MDE file for the front end?
> > Then if changes are required, I could distribute just the front end MDE
> > file.
> > Of course there will always be something changing in the tables too.
> > Basically looking to secure a work in progress and be able to modify a
> > customer's
> > program to suit.
> >
> >
> > "Alton" wrote:
> >
> >> I think that you should look at spliting the database into a front-end,
> >> back-end setup. This will allow you to make changes to the forms,
> >> queiries,
> >> macros and modules without having to disturb the backend or their daily
> >> operations. The book Real World Microsoft Access Database Protection and
> >> Security by Gary Robinson has been helpful for me. (ISBN: 1-59059-126-7)
> >> Hope this helps.
> >>
> >> "jptpjs" wrote:
> >>
> >> > I have created an Electronic Medical Program in Access.
> >> > I would like to distribute this program (sell), but I need it secure
> >> > with
> >> > the ability to
> >> > make changes or updates in the future. I read about MDE files which are
> >> > great but can these be updated or modified for the customer later?
> >> > I know I will probably need to include access runtime files and other
> >> > requirements.
> >> > This is my first shot at this kind of project.
> >> > Any help in the right direction will be appreciated.
> >> >
> >> > Thanks
> >> >
> >> >
>
>
>
.
- Follow-Ups:
- Re: Best way to distribute an Access Database
- From: Douglas J. Steele
- Re: Best way to distribute an Access Database
- References:
- Re: Best way to distribute an Access Database
- From: Douglas J. Steele
- Re: Best way to distribute an Access Database
- Prev by Date: Re: Packaging Wizard error -2147221163 more info
- Next by Date: Re: Best way to distribute an Access Database
- Previous by thread: Re: Best way to distribute an Access Database
- Next by thread: Re: Best way to distribute an Access Database
- Index(es):
Relevant Pages
|
Loading