Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook

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

Security between two workspaces

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

  • Security between two workspaces

    I have very little experience with AS security. I'm looking for some ideas on how to address this problem.

    I currently have two workspaces. The first work space contains data used for invoicing etc... I want to set up security on this workspace and it's database.

    The second workspace is not using workspace security. I created my own security as each user needs to log in to use the application. I use the login to filter the table used for data entry.

    The kink is that the second workspace reads from three tables and writes to another of the tables in the first workspace.

    I believe that if I set up security in the first workspace, the second workspace will be denied access to the first workspace.

    If that is the case, what would be my options to make this work? I need the second workspace to function seamlessly with the first.

    I think I could place the second database into the first workspace. But then it would require a user name and password to be entered twice. What my main objective is to allow certain users limited access to the invoicing application. Maybe I should make my own security login and depending on the user, disable buttons in the main menu? But then I was hoping to encrypt the data files in the invoicing app.

    I noticed there is an option to use the windows logon. Has anyone tried that?

    TIA,

    Ron
    Alpha 5 Version 11
    AA Build 2999, Build 4269, Current Build
    DBF's and MySql
    Desktop, Web on the Desktop and WEB

    Ron Anusiewicz

  • #2
    Re: Security between two workspaces

    We developed our own security years ago, an use a main menu application to "call" other individual applications. We use the addin.variables() space to hold the user-id, level of access, etc. Addin variables are unique in that they are available to whatever application needs them as long as Alpha 5 is open. Each application then has access to the user ID and access level, which makes security seameless throughout. I wrote an article in the alpha forum newsletter about our methodology. send me your e-mail address, and I will forward a copy.

    Tom
    Last edited by Tom Henkel; 10-23-2013, 10:34 AM. Reason: can't tpye

    Comment


    • #3
      Re: Security between two workspaces

      Originally posted by Ronald Anusiewicz View Post
      I think I could place the second database into the first workspace. But then it would require a user name and password to be entered twice. What my main objective is to allow certain users limited access to the invoicing application. Maybe I should make my own security login and depending on the user, disable buttons in the main menu? But then I was hoping to encrypt the data files in the invoicing app.
      Alpha's security will do what this sentence describes quite easily. One workspace, one login selected access level.
      Every user who logs in has been set as member of selected groups - in your case read group as "security clearance" level
      Any menu that calls invoices and/or on opening the invoice form (for example) can be restricted to selected group/s only.
      Selected user/s are made members of a group called "administrator" to control others' passwords, groups etc.
      Last edited by Ray in Capetown; 10-23-2013, 04:12 PM.

      Comment


      • #4
        Re: Security between two workspaces

        The kink is that the second workspace reads from three tables and writes to another of the tables in the first workspace.
        First, thank you Tom for your help. I read your article and was thinking about a course of action when I stumbled on the following function.

        Code:
        default_encryption_key_set("password")
        I put this into the autoexec of the second workspace. Now the second workspace runs totally seamless with the first. The second workspace already has it's own log in routine.
        Alpha 5 Version 11
        AA Build 2999, Build 4269, Current Build
        DBF's and MySql
        Desktop, Web on the Desktop and WEB

        Ron Anusiewicz

        Comment


        • #5
          Re: Security between two workspaces

          not a problem. Alpha didn't have security when we needed to set it up, so we needed to develop our own. Now, there is no reason to use Alpha's. Glad I could help.

          Tom

          Comment

          Working...
          X