Re: Distributing Runtime Only


"Ian Holder" <Ian Holder@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A921DDD8-1427-43C5-96D6-87B85BD77891@xxxxxxxxxxxxxxxx
> All,
>
> I have a database on a shared drive that three users shall be working
> with.
> Can I simply bundle up the files needed for runtime in an Installation
> Package and get the users to install it? Or do I need to have a database
> in
> an Installation Package?

Generally speaking, you would split your database into a frontend (forms,
reports, queries, macros, and modules) and backend (tables) and distribute
only the frontend (this would be the "database" you would distribute)... the
backend would stay on the server, and each user would connect their own
frontend to a common backend. So the only files needed to distribute would
be the frontend ... this is quite basic, as your frontend may have
dependancies that may not be present on the enduser machines ... if you used
any ActiveX controls you must make sure they are available, all references
must match up, etc etc ... deploying an app can be a big project.

Do your endusers have the correct version of Access installed? If so, you
only need to distribute the frontend ... if they do not have the correct
version, then you must distribute the Runtime (included in the Developers
edition) to each, and install it. Be warned, however, that doing this can
cause some unwanted effects ... if users don't need the runtime, don't
install it.


>
> Thanks,
> Ian.
>
>


.

Relevant Pages

  • Re: Split Database Security Problem
    ... Both frontend and backend ... > permissions, but as in all good stories there is a catch. ... The newAdmin for the 'object database' has the ...
    (comp.databases.ms-access)
  • RE: Form on front end loading slowly
    ... I gather the user has a frontend that uses a backend database on a server ... > have a database backend with a table that lists employees, ...
    (microsoft.public.access.formscoding)
  • Re: Split Database Security Problem
    ... Both frontend and backend ... > permissions, but as in all good stories there is a catch. ... The newAdmin for the 'object database' has the ...
    (comp.databases.ms-access)
  • Re: Multi users Logon Security questions
    ... > The next thing I need to do is split the database so others can work ... and navigate to the mdb - copy the mdb. ... You can use your desktop shortcut (which will open your frontend). ... Ctrl-O and open the backend mdb. ...
    (microsoft.public.access.security)
  • Split Database Security Problem
    ... I have managed to secure a split database. ... Both frontend and backend ... permissions, but as in all good stories there is a catch. ...
    (comp.databases.ms-access)