Announcement

Collapse

The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic


Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.


If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.


Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.



Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

How to password protect direct table access

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • How to password protect direct table access

    How can I password protect direct access to a table?

    I am not looking to password protect the table design rather password protect direct access to individual tables (i.e. keeping someone from just double clicking on them).

    I would like to do this without the use of a master password if possible.

    We have tables we prefer to have direct access to so it would be best if I could just place a password on individual tables, much like it is when you password protect the table designs.

    All ideas/feedback is appreciated.

  • #2
    Re: How to password protect direct table access

    keeping someone from just double clicking on them
    In what context? Windows, Alpha, ?
    There can be only one.

    Comment


    • #3
      Re: How to password protect direct table access

      From within Alpha.

      Comment


      • #4
        Re: How to password protect direct table access

        Why are they allowed to view the control panel and double click on tables if there are some you don't want opened that way?

        Easy to control the access by hiding the control panel and create browses and forms for the ones you want to be viewable.
        There can be only one.

        Comment


        • #5
          Re: How to password protect direct table access

          Originally posted by Scott Kurimski View Post
          ...
          I would like to do this without the use of a master password if possible.
          ...
          You need to use a master password. But you don't need to apply it through the
          standard Alpha UI which forces you to enter the password when opening the application. The work-around is to use an autoexec script which sets the master pwd. You will need to encrypt the tables using xbasic also (simple really).

          BUT, it sounds like all you really want is to keep users out of certain table. Hide the controlpanel and create a menu. In which case you will need to have two or more user names w. passwords to get into the app. Again, Alpha gives you this capability using their security framework - or you can build your own - simple or complex.
          Peter
          AlphaBase Solutions, LLC

          Peter@AlphaBaseSolutions.com
          https://www.alphabasesolutions.com


          Comment


          • #6
            Re: How to password protect direct table access

            Originally posted by Peter.Greulich View Post
            ...BUT, it sounds like all you really want is to keep users out of certain table. Hide the controlpanel and create a menu. In which case you will need to have two or more user names w. passwords to get into the app. Again, Alpha gives you this capability using their security framework - or you can build your own - simple or complex.
            Why would you need to use any security system other than a password protected button so the developer could access the control panel? I get the feeling we are thinking about two different situations here but I'm not clear about it.

            All I do is add a button with no text, no border, the 'tab order' box unchecked, and transparent fill. That button runs a script that prompts for a password in order to get to the control panel. (I do NOT like to use hotspots because they are too easy to find - just wave your cursor around until it changes to a finger. I know, it shouldn't matter as long as it's password protected. I guess I'm just anal and don't like the idea of users easily discovering my 'hidden' buttons. I don't think it looks professional to see the cursor changing for things that the user shouldn't be dealing with.)

            HINT: My script also checks the computer name using api_getmachinename() and bypasses the password when I'm working from my computer. I consider this "being lazy" - yes it takes a few extra seconds up front to add another section to the IF statement but it saves lots of time and frustration later on.

            Comment


            • #7
              Re: How to password protect direct table access

              I do NOT like to use hotspots because they are too easy to find
              I think you would like what I have done then in the past! my button is not only invisible but only 1 pixel square! unless you know exactly where it is placed, even if you knew there was a button somewhere, it would take a lot of trying to even just find it. :D
              Mike
              __________________________________________
              It is only when we forget all our learning that we begin to know.
              It's not what you look at that matters, it's what you see.
              Henry David Thoreau
              __________________________________________



              Comment


              • #8
                Re: How to password protect direct table access

                Now that's getting extreme!

                Here's another idea related to the use of api_getmachinename(). I use this to make a certain button effectively "smaller than one pixel".:D

                IF api_getmachinename() <> "MyComputerName"
                design_btn.hide()
                END IF

                I have a "developer's button" that does more than just get me to the control panel. It gives me the choice of going to the Control Panel, going directly to Design mode in the current form, going to the Code Editor, adding a special 'developer's toolbar' to a form, or jumping to any other form that is open. This button is on most of my forms in generic apps and some custom apps to make development work a bit faster and easier but the OnInit of the form hides it if it isn't on my computer. Even I can't get to it when working on a customer's computer. I don't need it there anyway because I can't get to Design mode or the Code Editor with the runtime - but I might need to get in to the control panel to fix some data so I have a separate button for that.

                Comment


                • #9
                  Re: How to password protect direct table access

                  Originally posted by CALocklin View Post
                  Why would you need to use any security system other than a password protected button so the developer could access the control panel? I get the feeling we are thinking about two different situations here but I'm not clear about it.
                  I might have been making too much out of it. Two different scenarios - yes.

                  Originally posted by CALocklin View Post
                  - just wave your cursor around until it changes to a finger.
                  You mean until it GIVES you the finger! :mad:
                  Peter
                  AlphaBase Solutions, LLC

                  Peter@AlphaBaseSolutions.com
                  https://www.alphabasesolutions.com


                  Comment

                  Working...
                  X