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 setup mssing for FORMs & Reports

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

    Security setup mssing for FORMs & Reports

    Afternoon.

    My client is trying to set security in his application. He can set it on a DBF but there is NO setup for "Forms or Reports". They are running the latest 10.5 runtime.

    They tell me that in v8 they could do this.

    I could use HELP as to why they can't.

    Thanks.

    dew

    #2
    Re: Security setup mssing for FORMs & Reports

    This same problem cropped up BEFORE back in 2008 when we were running v8 & intalled the latest v8 patch. We had to reinstall the OLDER patch to get the security setup back again.

    I thought maybe too much vino or a fuzzy memory thinking that setting security on Forms & Reports was not available with v8 runtime.

    As a test, I installed an older app (vintage 2008) that used patch 3156. Eureka, a user could set the security on forms & reports.

    See 3 attached pics.

    Now I know why our client was very upset when they upgraded to v10.5 as now they can not change the permission on various Forms & Reports. Have I missed something?

    Anything I can do other than tell them they need to puchase the developer package. Would not want to hear their reaction....

    dewayne

    Originally posted by dchiass View Post
    Afternoon.

    My client is trying to set security in his application. He can set it on a DBF but there is NO setup for "Forms or Reports". They are running the latest 10.5 runtime.

    They tell me that in v8 they could do this.

    I could use HELP as to why they can't.

    Thanks.

    dew

    Comment


      #3
      Re: Security setup mssing for FORMs & Reports

      D, I've confirmed the same behavior here using build 3432_3608. Suggest a formal bug report be submitted.

      Comment


        #4
        Re: Security setup mssing for FORMs & Reports

        D,

        I have misgivings about letting runtime users change security settings in the application. Shouldn't this only be done using the developer version?

        Comment


          #5
          Re: Security setup mssing for FORMs & Reports

          Every user we have that uses security, want something "unique" in their security setup. It would be impossible for us to support them everytime they wanted to change something.

          Is there a reason to force them to BUY the deveoper version. This was NOT the case, back in v8 as I mentioned. To me them having the "developer" edition would cause us many more misgivings as they can then change dbf structures & do some all sorts of changes in the sandbox.

          dewayne

          PS, do you have the LINK for reporting a bug? Thanks.

          Originally posted by Tom Cone Jr View Post
          D,

          I have misgivings about letting runtime users change security settings in the application. Shouldn't this only be done using the developer version?

          Comment


            #6
            Re: Security setup mssing for FORMs & Reports

            Originally posted by dchiass View Post
            Every user we have that uses security, want something "unique" in their security setup. It would be impossible for us to support them everytime they wanted to change something.

            Is there a reason to force them to BUY the deveoper version. This was NOT the case, back in v8 as I mentioned. To me them having the "developer" edition would cause us many more misgivings as they can then change dbf structures & do some all sorts of changes in the sandbox.

            dewayne

            PS, do you have the LINK for reporting a bug? Thanks.

            the runtime should NOT expose the security menu. it was a bug that it ever did. this is now fixed.

            Comment


              #7
              Re: Security setup mssing for FORMs & Reports

              You reply indicates that our user (or users) would need to buy the full developer edition if they want to change the security on "one form" of our application?

              If it was a bug, why is "set security" in runtime still working for DBF's ?

              Thanks.

              dewayne

              Originally posted by Selwyn Rabins View Post
              the runtime should NOT expose the security menu. it was a bug that it ever did. this is now fixed.

              Comment


                #8
                Re: Security setup mssing for FORMs & Reports

                Originally posted by dchiass View Post
                You reply indicates that our user (or users) would need to buy the full developer edition if they want to change the security on "one form" of our application?

                If it was a bug, why is "set security" in runtime still working for DBF's ?

                Thanks.

                dewayne
                the 'set security on a table' option should not have been available in the runtime. it was an error on our part that it ever was. it has now been removed.

                Comment


                  #9
                  Re: Security setup mssing for FORMs & Reports

                  Can you recommend the easiest way for us to change the security on one form for this client? For us, to make this security change is easy.

                  What files would we need to send them?

                  At present they have a CUSTOM security setup which they are happy with (on some forms & dbf's). I am sure they would be upset if the files we sent with this 1 change, overwrote all their changes.

                  dew

                  Originally posted by Selwyn Rabins View Post
                  the 'set security on a table' option should not have been available in the runtime. it was an error on our part that it ever was. it has now been removed.

                  Comment


                    #10
                    Re: Security setup mssing for FORMs & Reports

                    Why do you have misgivings? We have about 12 users that have setup their own security on various Forms in our application.

                    Our application has various modules: machines, parts, work orders, purchase orders, employees, pm tasks and more.

                    Depending on each users needs, they "were" setting security usually on various forms. Thus the mechanic was not able to go into the Purchase Order or Employee modules. A purchaser was not able to go into the Machine or Employee module. This setup was for 1 user and their needs were specific.

                    They had no trouble setting security on the various forms and testing it to see if it did what they expected.

                    Client #2 mite have a slightly different need.

                    How could we as a developer, pre-set every scenario that mite crop up? Impossible.

                    We are surprised that Selwyn indicated that allowing a user to set security in the runtime (as was the case in an older v8) was a BUG....

                    We have developed a generic setup for security in our application which works for 3/4 of our clients but its those other 25% with specific needs (maybe on ONE form only) that causes us a problem.

                    Without asking them to buy the full development version, how do you suggest we handle this clients minimal request? I did ask this on my last post but as yet received no reply.

                    Any suggestions are greatly appreciated!!!! We are stuck.

                    Thanks for the help & your replies are always welcomed.

                    Originally posted by Tom Cone Jr View Post
                    D,

                    I have misgivings about letting runtime users change security settings in the application. Shouldn't this only be done using the developer version?

                    Comment


                      #11
                      Re: Security setup mssing for FORMs & Reports

                      Security Functions
                      http://support.alphasoftware.com/alp..._Functions.htm

                      A5_Change_Permission()
                      http://support.alphasoftware.com/alp...SION%28%29.htm
                      Andrew

                      Comment


                        #12
                        Re: Security setup mssing for FORMs & Reports

                        Thanks for the post.

                        I am not sure if what you posted allows one of our clients running the runtime to set security "on their own".

                        In a previous v8 runtime, they right clicked on either a DBF, Form or Report and could set up security for various groups & users. Their IT department found that "fairly" easy to understand & do if a Manager wanted some permissions changed.

                        Now unless, I don't understand, this same user will need to purchase the full development version to make permission changes.

                        dewayne

                        Comment


                          #13
                          Re: Security setup mssing for FORMs & Reports

                          Originally posted by dchiass View Post
                          Thanks for the post.

                          I am not sure if what you posted allows one of our clients running the runtime to set security "on their own".

                          In a previous v8 runtime, they right clicked on either a DBF, Form or Report and could set up security for various groups & users. Their IT department found that "fairly" easy to understand & do if a Manager wanted some permissions changed.

                          Now unless, I don't understand, this same user will need to purchase the full development version to make permission changes.

                          dewayne
                          You can use the functions I linked in a runtime environment to manipulate the security on forms. In this case you will need to code an xbasic script that allows the user to select a form, select a user or group, and then specify the level of security needed. Your script will then call the A5_Change_Permission() function passing the information selected by the user.
                          Andrew

                          Comment


                            #14
                            Re: Security setup mssing for FORMs & Reports

                            Thanks for that!!!! I will kick the ball to our programmer. Obviously he has some work to replace what Alpha removed as a "bug"....

                            dewayne

                            Originally posted by aschone View Post
                            You can use the functions I linked in a runtime environment to manipulate the security on forms. In this case you will need to code an xbasic script that allows the user to select a form, select a user or group, and then specify the level of security needed. Your script will then call the A5_Change_Permission() function passing the information selected by the user.

                            Comment


                              #15
                              Re: Security setup mssing for FORMs & Reports

                              Why do you have misgivings? We have about 12 users that have setup their own security on various Forms in our application
                              DeWayne, I have misgivings any time the runtime user has access to the control panel, including any time a runtime user can change the security setting for the application by right clicking on a table, form, report or other object. Makes the hair on the back of my neck stand up imagining the call I will receive when a disgruntled, angry, or ignorant user does a lot of damage.

                              I think most of my customers would want me as designer to protect their investment in the database from their own users, instead of simply pointing all runtime users to the control panel and the right click context menu.

                              Comment

                              Working...
                              X