Results 1 to 12 of 12
  1. #1
    2 Star Lounger
    Join Date
    Feb 2001
    Location
    San Francisco, CA, USA
    Posts
    184
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Security-Macros (2002)

    I do not want my client to see my macos. I tried using the user security wizard and got wrapped aroung a pole.
    I going to copy my database and bring it to my customer but to do want her to seem them.
    Not quite sure how to set security for this.
    Frank

  2. #2
    Silver Lounger
    Join Date
    Jan 2001
    Location
    Indianapolis, Indiana, USA
    Posts
    1,862
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Security-Macros (2002)

    Frank, have you checked the Access helpfiles? <img src=/S/rtfm.gif border=0 alt=rtfm width=24 height=23> There is an explanation on how to Secure a database without requiring your users to log on.

    In the Contents section of the helpfiles, look for:

    Administering and Securing an Access File > Securing a Database > Secure an Access database and its objects with user-level security

    An alternative would be to write everything in code and create an MDE file. All code will be compiled and can not be viewed or changed by the user.

    HTH

  3. #3
    2 Star Lounger
    Join Date
    Feb 2001
    Location
    San Francisco, CA, USA
    Posts
    184
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Security-Macros (2002)

    Thanks Mark
    I will check that out.
    I have 97 and 2002 on my computer. I have saved it in 2000 format and it will not let me make an MDE file.
    I think I had some problems when I installed 97 back on the computer and not sure what will have if I install 2000 now maybe nothing.
    Lucklily my client baled out today so I have some time to secure the macro's hopefily with just a password.
    Frank

  4. #4
    Silver Lounger
    Join Date
    Jan 2001
    Location
    Indianapolis, Indiana, USA
    Posts
    1,862
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Security-Macros (2002)

    I've never tried installing an older version AFTER a new version of Office. I always start with 97, then 2000, then 2002.

    If done properly the will all play nicely together. One trick is that you must install Office 97 into a totally separate Program folder (I use C:Program FilesOffice97).

    You can install Office 2000 to the default folder (C:Program FilesMicrosoft Office). Office 2002 will even allow you to install it to the same folder as Office 2000 - it creates its own subfolder (Office 10).

    I'm not sure what to tell you about the MDE. Sometimes if there is a problem compiling code the MDE will fail to make. Or maybe Access 2002 will only produce 2002 format MDEs. I'm sure another Lounger will be able to help you out with that...

  5. #5
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: Security-Macros (2002)

    In Access 2000 and later, you can also password protect your code modules, including the code behind forms. To do so, you go into the VBE and select the project properties item from the Tools menu. One of the tabs is Protection, which will allow you to turn on code protection and enter and confirm a password so *you* can get into the code.
    Charlotte

  6. #6
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: Security-Macros (2002)

    I wouldn't recommend installing 2000 after XP. I can be done, but the VB editor library got updated in OXP, and it can toast your Access 2000 code projects if you aren't very, very careful. The problems with that have been discussed extensively in General Office Solutions.
    Charlotte

  7. #7
    2 Star Lounger
    Join Date
    Feb 2001
    Location
    San Francisco, CA, USA
    Posts
    184
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Security-Macros (2002)

    My project does not have any modules. Mostly macros and code behind the forms.
    I need someone to hold my hand on the password user wizard. I deselected macros and created a user but it won't let me into any objects.
    <img src=/S/scratch.gif border=0 alt=scratch width=25 height=29>

  8. #8
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: Security-Macros (2002)

    The code behind a form is a module and you can password protect those. There is no real reason to protect macros because they are so primitive that pretty much anyone can recreate them without bothering to steal them. There is a security whitepaper available from Microsoft and a Lounge search will turn up plenty of references to it.
    Charlotte

  9. #9
    2 Star Lounger
    Join Date
    Feb 2001
    Location
    San Francisco, CA, USA
    Posts
    184
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Security-Macros (2002)

    Yes, but how do you secure my "primitive" macro's.
    I don't quite understand how to set up admin and user accounts and permissions.
    ALL I want to do is secure from viewing my macros and secondarily the code behind my forms-humor me please.
    Frank

  10. #10
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: Security-Macros (2002)

    You're going to have to read the Security FAQ for Access and use the security wizard on the database. I can't help you with that because you have to do it on the database you're working with.
    Charlotte

  11. #11
    2 Star Lounger
    Join Date
    Feb 2001
    Location
    San Francisco, CA, USA
    Posts
    184
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Security-Macros (2002)

    Thanks Was a little confused on admin. users groups etc.
    Frank

  12. #12
    Bronze Lounger
    Join Date
    Nov 2001
    Location
    Arlington, Virginia, USA
    Posts
    1,394
    Thanks
    0
    Thanked 3 Times in 3 Posts

    Re: Security-Macros (2002)

    Another option if you want to hide macros & other database objects from users without creating .MDE file or implementing Access security is to set Startup options so they cannot view database window. Attached screen capture shows recommended settings. In particular you want to clear options for "Display Database Window" and "Use Access Special Keys". For this approach to work, you will need to have a main switchboard or startup form to be displayed when app is opened in place of database window. You will also need to create a custom Menu bar to replace the built-in one and specify this menu in Menu Bar box in place of "default". (Optionally you can also create custom Shortcut Menu.) When creating custom menu take care to include all commands necessary to use app, while excluding those commands that would allow user to access database. A customer would not appreciate an app that is "crippled" because you forgot to include some necessary menu command. Ensure the Hide & Unhide commands (Window menu) are not available to users; the Unhide command can be used to unhide hidden database window. The Database Window command obviously should not be available to user. It's also important to disable "Allow Built-in Toolbars" and "Allow Toolbar/Menu Changes" so user cannot circumvent these precautions. For more info on custom menus & toolbars, and on setting Startup options, see Help.

    One last step after setting Startup options is to disable Shift Bypass Key so knowledgeable user cannot bypass your Startup settings by opening database with Shift key. A recent thread discussed this topic, I posted a reply with sample db attached that demonstrated how this works: <!post=Re: AllowBypassKey (2002 (XP)),181926>Re: AllowBypassKey (2002 (XP))<!/post>

    One final note, whatever you do to secure database, whether using Access security, .MDE files, password protection, or Startup options, use a BACKUP copy of your database so you don't wind up locked out of your own database!!

    HTH
    Attached Images Attached Images

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •