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

alternatives to full development-edition to set form security?

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

    alternatives to full development-edition to set form security?

    Since the security setup was REMOVED from the runtime version many years ago, what is the alternative to the users of our application to set permissions (deny/grant) on forms & DBF's.

    We do not want to give a user any method to go into the application & start changing dbf structures, field rules, report layouts and other functions that could lead them into murky waters. They would be able to do this if they purchased the development-edition.

    Thanks.

    #2
    Re: alternatives to full development-edition to set form security?

    If they have the develpment version and copy your files to a new directory and add them to the new adb, I don't think there is anything that will prevent them from accessing those tables. You could however password protect your layouts which means they would have to create their own. And if all your scripts are compiled into an AEX file, that keeps them out of them. Do you suspect a client of wanting to steal your application as the basis for creating their own?

    Dave Mason may have some ideas...
    Robin

    Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

    Comment


      #3
      Re: alternatives to full development-edition to set form security?

      Originally posted by MoGrace View Post
      If they have the develpment version and copy your files to a new directory and add them to the new adb, I don't think there is anything that will prevent them from accessing those tables. You could however password protect your layouts which means they would have to create their own. And if all your scripts are compiled into an AEX file, that keeps them out of them. Do you suspect a client of wanting to steal your application as the basis for creating their own?

      Dave Mason may have some ideas...
      I did not explain it very good as your reply shows.

      1.a user has our application.
      2.they develop their own list of groups/users & passwords for forms & databases
      3.every so often we send them an UPGRADE of our application.
      4.here is the critical part, IF they do not export their security settings before the upgrade they will be lost & they will end up with our "generic" ones.
      5.their process is export groups/users etc before the upgrade
      6.after the upgrade is done, they import the groups/users & their passwords back in. These overwrite the "generic" ones we have in the upgrade.exe

      It has nothing to do with codes, layouts or stealing our application.

      Almost 100% do not want / need or have the alpha's development edition BUT they want control over what each group/user has permission to do. Such as which group can view certain forms or which groups can do certain functions (add, change, view, delete) on the data.

      I hope that this does not muddy the waters more with my explanation. If not, I will try again!!!

      Comment


        #4
        Re: alternatives to full development-edition to set form security?

        Here is what I see in my development-edition
        Sec Form Pic01.bmpSec Form Pic021.bmp

        I would like a user of our APP to be able to view the settings on a security module within our app. This is what a user can see after THEY Set Security. We are very close* as the pic below shows.
        Sec Form in App Pic01.jpg

        *but sometimes what a user sees is NOT what he set. Seems the little boxes do not get updated though when we look at the security settings with the development-edition they are correct.

        Does that make sense?

        Comment

        Working...
        X