>As the FE is distributed to the end users within the network, is it possible
>to protect the code of the FE in some way? Basically, I don't want the users
>to be able to see the code and modify it (if that is possible)
Create an MDE and distribute the MDE to the users. Note that you
*MUST* keep the MDB so you can make changes to it and then make the
MDE again.
Tony

Signature
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
> As the FE is distributed to the end users within the
> network, is it possible to protect the code of the FE
> in some way? Basically, I don't want the users
> to be able to see the code and modify it (if that
> is possible)
If it is only the code that you want to protect, Tony's suggestion is the
proper approach -- distribute an MDE (or Access 2007 ACCDE). However, if
you also want to protect the other objects (for example, Queries, any Tables
you may have put in the FE, and Macros), you can use User/Group Level
security.
If you choose User/Group Level secur, be sure not to just rely on the Help
and the Security Wizard, but go to the Microsoft support site, search for,
and download the Access Security FAQ. Read, re-read, study carefully and
then experiment on copies of your database -- it is quite a numer of pages,
full of information, with no filler material.
Larry Linson
Microsoft Access MVP
Tom Wickerath MDB - 24 May 2007 04:31 GMT
you guys are WRONG
this doesn't allow you to secure your QUERIES
using access data projects will allow you to use encryption on the DDL for
views and sprocs
don't bother selling a solution based on MDB; MDB won't even run on x64
machiens.. right?
> > As the FE is distributed to the end users within the
> > network, is it possible to protect the code of the FE
[quoted text clipped - 16 lines]
> Larry Linson
> Microsoft Access MVP
'69 Camaro - 24 May 2007 04:54 GMT
Everyone please note that Aaron Kem.pf is attempting to impersonate one of
our regular posters again. Tom would never post such a message.
HTH.
Gunny
See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blogs: www.DataDevilDog.BlogSpot.com, www.DatabaseTips.BlogSpot.com
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact
info.
> you guys are WRONG
>
[quoted text clipped - 26 lines]
>> Larry Linson
>> Microsoft Access MVP
Tom Wickerath - 24 May 2007 08:35 GMT
tom doesn't have the mental capacity to learn SQL Server
tom doesn't have the mental capacity to learn SQL Server
tom doesn't have the mental capacity to learn SQL Server
tom doesn't have the mental capacity to learn SQL Server
> Everyone please note that Aaron Kem.pf is attempting to impersonate one
> of our regular posters again. Tom would never post such a message.
[quoted text clipped - 38 lines]
>>> Larry Linson
>>> Microsoft Access MVP
'69 Camaro - 24 May 2007 09:09 GMT
Everyone please note that Aaron Kem.pf is attempting to impersonate one of
our regular posters again. Tom would never post such a message.
HTH.
Gunny
See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blogs: www.DataDevilDog.BlogSpot.com, www.DatabaseTips.BlogSpot.com
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact
info.
<SNIPPED>
>> Everyone please note that Aaron Kem.pf is attempting to impersonate one
>> of our regular posters again. Tom would never post such a message.
[quoted text clipped - 38 lines]
>>>> Larry Linson
>>>> Microsoft Access MVP
Diego Arbe - 24 May 2007 06:53 GMT
Larry,
Thank you for your suggestion.
I will download the guide and start experimenting.
Thank you once again,
Regards,
Diego
> > As the FE is distributed to the end users within the
> > network, is it possible to protect the code of the FE
[quoted text clipped - 16 lines]
> Larry Linson
> Microsoft Access MVP
You most certainly can, and should hide all of the ms-access interface. The
options to complete hide and keep people out of the ms-access interface can
easily be done using the tools->start-up options. Using those options allows
you to complete hide the ms-access interface (tool bars, database window
etc). Also, using these options means you
do not have to bother setting up security.
Try downloading and running the 3rd example at my following web site that
shows a hidden ms-access interface, and NO CODE is required to do
this....but just some settings in the start-up.
Check out:
http://www.members.shaw.ca/AlbertKallal/msaccess/DownLoad.htm
After you try the application, you can exit, and then re-load the
application, but hold down the shift key to by-pass the start-up options. If
want, you can even disable the shift key by pass. I have a sample mdb file
that will let you "set" the shift key bypass on any application you want.
You can get this at:
http://www.members.shaw.ca/AlbertKallal/msaccess/msaccess.html

Signature
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pleaseNOOSpamKallal@msn.com
Diego Arbe - 29 May 2007 21:44 GMT
Thank you albert!
This is exactly what I needed.
I am starting to implement it for my next distribution.
Regards,
Diego
> You most certainly can, and should hide all of the ms-access interface.
> The options to complete hide and keep people out of the ms-access
[quoted text clipped - 17 lines]
> want. You can get this at:
> http://www.members.shaw.ca/AlbertKallal/msaccess/msaccess.html