Jumat, 25 Oktober 2013

RE: Re: [MS_AccessPros] RE: block deletion of record

 

Daniel


There are lots of steps to secure an ACCDE file. First, you create a custom ribbon and select it as the default ribbon. Using a USysRibbon table, you write the XML. In the XML, you make the File tab pretty much a blank tab. Here is my main Ribbon's XML.


<customUI xmlns="http://schemas.microsoft.com/office/2009/07/customui">

    <ribbon startFromScratch="true">


        <tabs>

            <tab id="tabMain" label="Main">

            </tab>

        </tabs>

    </ribbon>

    <backstage>

        <tab idMso="TabInfo" visible="false"/>

        <button idMso="FileSave" visible="false"/>

        <button idMso="SaveObjectAs" visible="false"/>

        <button idMso="FileSaveAsCurrentFileFormat" visible="false"/>

        <button idMso="FileOpen" visible="false"/>

        <button idMso="FileCloseDatabase" visible="false"/>

        <tab idMso="TabRecent" visible="false"/>

        <tab idMso="TabNew" visible="false"/>

        <tab idMso="TabPrint" visible="false"/>

        <tab idMso="TabShare" visible="false"/>

        <tab idMso="TabHelp" visible="false"/>

        <button idMso="ApplicationOptionsDialog" visible="false"/>

        <button idMso="FileExit" visible="false"/>

    </backstage>


</customUI>


A good place for more info on Ribbon XML is at www.accessribbon.de/en/index.php?Access_-_Ribbons


I use a blank ribbon because all my navigation is done through a form like the Switchboard form.


Next, you disallow shortcut menus (context menus) so a use cannot right click on something and get to things you don't want them to see.


The code I use to set all the database properties is used by most developers. There is a sample in our Files>1_Samples named StartupFormForMDE. The code works for ACCDEs, too. What it does is use the startup form to set the database properties to tighten up most stuff that keeps users out of the tables, queries, etc. When you make an ACCDE and run it the first time, those settings are set. The next time the file is opened the user is restricted to do just about nothing but say on the forms.


Lastly, you can set up a database with even more restrictions using code that Allen Browne wrote. You can find it at http://allenbrowne.com/ser-69.html


Doing all this stuff should keep your database safe, at least from everyone but Access developers.







---In MS_Access_Professionals@yahoogroups.com, <ms_access_professionals@yahoogroups.com> wrote:

ok, thanks,

I unchecked "Display Navigation Pane" but any user can still check that back, even when you make a ACCDE file
is there a way to lock these options?


thanks,
Daniel



On Thursday, October 24, 2013 2:57:13 AM, Glenn Lloyd <argeedblu@gmail.com> wrote:
 
This post at UtterAccess.com has a good discussion with a utility attached for securing the back end about as well as can be done. Several versions of code to prevent shift-key bypass are available on the net including this one, again at UtterAccess.
 
Glenn
 
From: MS_Access_Professionals@yahoogroups.com [mailto:MS_Access_Professionals@yahoogroups.com] On Behalf Of Dan Abc
Sent: Wednesday, October 23, 2013 6:44 PM
To: MS_Access_Professionals@yahoogroups.com
Subject: Re: [MS_AccessPros] RE: block deletion of record
 
 
no, how to do that?
 
I can un-check show all access objects, but that can be changed later by users
I do make a ACCDE file
 
On Wednesday, October 23, 2013 3:36:44 PM, Glenn Lloyd <argeedblu@gmail.com> wrote:
 
Daniel,
 
Are you hiding the navigation pane and preventing shift key bypass? Are people getting to the backend and opening it directly?
 
Glenn
 
From: MS_Access_Professionals@yahoogroups.com [mailto:MS_Access_Professionals@yahoogroups.com] On Behalf Of Dan Abc
Sent: Wednesday, October 23, 2013 6:32 PM
To: MS_Access_Professionals@yahoogroups.com
Subject: Re: [MS_AccessPros] RE: block deletion of record
 
 
how to prevent access to table?
 
 
in my DB with forms I have only linked tables, but anyone can still open the table and add/delete records
 
 
On Wednesday, October 23, 2013 1:04:46 PM, "wrmosca@comcast.net" <wrmosca@comcast.net> wrote:
 
Daniel
 
Yes...Don't give them direct access to the tables EVER. All users should have to use forms for everything. With a form it's easy to set its Allow Deletions to No. Other properties are Allow Additions, Allow Edits.
 
Hi All,
 
 
Is there a way to prevent anyone from deleting a record in a table?
 
 
Thanks,
Daniel
 
 
 


__._,_.___
Reply via web post Reply to sender Reply to group Start a New Topic Messages in this topic (10)
Recent Activity:
.

__,_._,___

Tidak ada komentar:

Posting Komentar