Runtime and Split Database

Thanks for the reply Bonnie. I am not 100% sure what I mean. Most users
will not have Access on the computers. I am guessing that an MDE would then
not work. Correct?

Thanks.

"bhicks11 via AccessMonster.com" wrote:

> Do you mean an MDE? Microsoft has a runtime version of Access that can be
> included with an app when users don't have a full verions but I think you
> mean a compiled MDE.
>
> If so, heres a linke:
>
> http://www.tek-tips.com/faqs.cfm?fid=91
>
> You split the MDB and then compile the front end to an MDE. Make sure you
> keep your MDB backed up. Your tables are linked automatically but if you
> ever have problems you can go back to your MDB and relink. Keep everything
> backed up. I think you will find it works well.
>
>
> Bonnie
> http://www.dataplus-svc.com
>
> PBISMaryland wrote:
> >Hi. I am getting myself a bit confused and thought a post may clear it a bit.
> >
> >I have an Access database that I would like to distribute but do not what
> >users to be able to modify objects. Using a runtime version seems to have
> >solved that issue but I am interested in possibly splitting the database so
> >more than one user can access the backend. However, when I create the
> >runtime version how can I then connect to the back end through that
> >application. Sorry if this post sounds confusing but I am confused myself.
> >
> >Bottom line: what steps should/could I take to allow more than one user to
> >use the application while protecting the objects from being changed or
> >deleted.
> >
> >Thanks in advance.
>
> --
> Message posted via AccessMonster.com
> http://www.accessmonster.com/Uwe/Forums.aspx/access-setupconfig/200808/1
>
>

PBISMaryland wrote:
> Thanks for the reply Bonnie. I am not 100% sure what I mean. Most
> users will not have Access on the computers. I am guessing that an
> MDE would then not work. Correct?

The use of an MDE and the use of the runtime have nothing to do with each
other.

An MDE prevents viewing or altering code or code-based objects (forms,
reports, modules). It does this because the human readable code has been
compiled to a non-readable format and the readable part is stripped out of
the file.

The runtime is a "run-only" version of Access that lets users who don't have
a retail copy of Access use Access applications. Using that does nothing to
protect your design (unless you also use an MDE) because even if you
distribute your file with the runtime, that does nothing to prevent a user
with a full copy of Access from opening it. Your design would be safe from
users who had ONLY the runtime installed.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com

An mde will run with Access runtime. What did you mean when you said runtime?


Bonnie
http://www.dataplus-svc.com

PBISMaryland wrote:
>Thanks for the reply Bonnie. I am not 100% sure what I mean. Most users
>will not have Access on the computers. I am guessing that an MDE would then
>not work. Correct?
>
>Thanks.
>
>> Do you mean an MDE? Microsoft has a runtime version of Access that can be
>> included with an app when users don't have a full verions but I think you
>[quoted text clipped - 26 lines]
>> >
>> >Thanks in advance.

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/Forums.aspx/access-setupconfig/200808/1

The users will most likely not have Access on their computers. I thought
then that the only way they can run the application I created was if they
then had the runtime version of Access. In an ideal world here is what I am
trying to accomplish:

I would like to have data stored on a server and have from 1 - 5 users (who
do not have a full version of Access) have the front-end on their computers.
I also do not want them to have access to modify or create reports or forms.

"bhicks11 via AccessMonster.com" wrote:

> An mde will run with Access runtime. What did you mean when you said runtime?
>
>
> Bonnie
> http://www.dataplus-svc.com
>
> PBISMaryland wrote:
> >Thanks for the reply Bonnie. I am not 100% sure what I mean. Most users
> >will not have Access on the computers. I am guessing that an MDE would then
> >not work. Correct?
> >
> >Thanks.
> >
> >> Do you mean an MDE? Microsoft has a runtime version of Access that can be
> >> included with an app when users don't have a full verions but I think you
> >[quoted text clipped - 26 lines]
> >> >
> >> >Thanks in advance.
>
> --
> Message posted via AccessMonster.com
> http://www.accessmonster.com/Uwe/Forums.aspx/access-setupconfig/200808/1
>
>

So compile the MDE for their desktops and install it with the runtime for
those that don't have Access on the PC's. There are a few considerations
that you should consider in regard to the MDE. Search help and review it
before compiling.

Bonnie
http://www.dataplus-svc.com

PBISMaryland wrote:
>The users will most likely not have Access on their computers. I thought
>then that the only way they can run the application I created was if they
>then had the runtime version of Access. In an ideal world here is what I am
>trying to accomplish:
>
>I would like to have data stored on a server and have from 1 - 5 users (who
>do not have a full version of Access) have the front-end on their computers.
>I also do not want them to have access to modify or create reports or forms.
>
>> An mde will run with Access runtime. What did you mean when you said runtime?
>>
>[quoted text clipped - 12 lines]
>> >> >
>> >> >Thanks in advance.

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/Forums.aspx/access-setupconfig/200808/1

I think you have received some cofusing thought mostly correct information.
I am posting in hopes I can clarify it some.

First about splitting a database.
You should always deploy your applications as split databaes. There are
multiple reasons to do do. The correct implemention is for each user to have
their own copy of the front end linked to the backend in a shared folder
where they have read, write, and delete privledges. These are important
because of the ldb file that is created, updated, and deleted when using an
access application.

I also recommend you use UNC paths rather than Drive Map paths when linking
to the back end. It is more efficient and it prevents any problems when all
users don't have the save drive letter mapped to the backed mdb location.

For those users who do not have a full install of Acces, you can install the
Access runtime which only allows execution of an Access application. No
changes to any Access objects is allowed. It has to be installed on each
user's computer.

It is not necessary to install Access or any other supporting software on
the server. Access is a file server database engine, not a client server
application like SQL Server. That means, that there is no requirement for
any software running on the server for an Access applicaiton. All the logic
and processing occur on the user's computer. That is the main reason it is a
bad idea to share one copy of an unsplit database or even one copy of a front
end database on the server. It is a much heavier impact on network traffic
and almost assures you will sooner or later have corruption in your database.

The decision as to whether to deploy the mdb or an mde to the users is up to
you. I recommend deploying only an mde, particularly if you have any users
with full Access installed.
--
Dave Hargis, Microsoft Access MVP


"PBISMaryland" wrote:

> The users will most likely not have Access on their computers. I thought
> then that the only way they can run the application I created was if they
> then had the runtime version of Access. In an ideal world here is what I am
> trying to accomplish:
>
> I would like to have data stored on a server and have from 1 - 5 users (who
> do not have a full version of Access) have the front-end on their computers.
> I also do not want them to have access to modify or create reports or forms.
>
> "bhicks11 via AccessMonster.com" wrote:
>
> > An mde will run with Access runtime. What did you mean when you said runtime?
> >
> >
> > Bonnie
> > http://www.dataplus-svc.com
> >
> > PBISMaryland wrote:
> > >Thanks for the reply Bonnie. I am not 100% sure what I mean. Most users
> > >will not have Access on the computers. I am guessing that an MDE would then
> > >not work. Correct?
> > >
> > >Thanks.
> > >
> > >> Do you mean an MDE? Microsoft has a runtime version of Access that can be
> > >> included with an app when users don't have a full verions but I think you
> > >[quoted text clipped - 26 lines]
> > >> >
> > >> >Thanks in advance.
> >
> > --
> > Message posted via AccessMonster.com
> > http://www.accessmonster.com/Uwe/Forums.aspx/access-setupconfig/200808/1
> >
> >