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

Form not locked down

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

    #16
    Re: Form not locked down

    I tested on 10.5 and 11 and the limitation is there, too
    In Selwyns example, use a separator instead and nothing will show
    Cole Custom Programming - Terrell, Texas
    972 524 8714
    [email protected]

    ____________________
    "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

    Comment


      #17
      Re: Form not locked down

      Martin,

      Thanks for the 'separator' idea from Selwyn's example. That's a little cleaner fix to his workaround.

      ba

      Comment


        #18
        Re: Form not locked down

        Interesting caveat to anyone considering using Selwyn's suggestion from above. It does work, BUT it will make the change on ANY app you run on that PC AND it will be there whether the app is opened or running under the Runtime or Developer's edition. In other words this change for some reason is GLOBAL across all A5 apps running on the same PC.

        Comment


          #19
          Re: Form not locked down

          Originally posted by Bob Arbuthnot View Post
          Interesting caveat to anyone considering using Selwyn's suggestion from above. It does work, BUT it will make the change on ANY app you run on that PC AND it will be there whether the app is opened or running under the Runtime or Developer's edition. In other words this change for some reason is GLOBAL across all A5 apps running on the same PC.

          But it appears that the fix only affects one pc but no one else accessing the database. In other words, you will need to apply the suggestion to all the user's PC's. I do not think it would make sense on a multi user LAN unless there is way to push the changes to all users via a script??

          Comment


            #20
            Re: Form not locked down

            Bob,

            I have enclosed the Screen Shots for you. I hope it will help you.

            I also notice that pressing the F3 key on the keyboard puts the form in 'change' mode.
            Restrict01.jpgrestrict02.jpgrestrict03_save.jpg

            Step 1 - Applied the "Form property" set which is same as this and I prefer use "form Property" instead of use "this code on the Event"
            'Preventing any changes to a form
            'Perhaps you want to prevent the user from making any changes on your form. That is simple in Xbasic. The
            'new properties we will use are:
            '<form_pointer>.restrict_enter = .t. ' No enters allowed at form level
            '<form_pointer>.restrict_change = .t. ' No changes allowed at form level
            'which are akin to changing the properties of the form in design mode, and the property
            '<browse_name>.browse.readonly = .t. ' No enters or changes allowed for invoice header browse
            Step 2 - each button has the code as you wish to have the action such as edit, delete, save ... and "restrict" again.

            Final -- You are not able to change, delete the record from current form even you selected from A5 menu or pressed "F3".

            Comment


              #21
              Re: Form not locked down

              John,

              I posted a way to disable the F3 button above.

              In your example of Step 2, is your conditional object hidden on the form? If not, then make it so and then right click on the area where the CO resides. Does the right click menu appear with the options to enter, change, or save? If so, then the user can effectively bypass the buttons you have placed on the form and by doing so they will bypass any extra code you may have on those buttons.

              Comment


                #22
                Re: Form not locked down

                Bob,

                I did for your
                What else can I do to finish locking this form down the way I need it to be?
                I did not know you are looking for
                a way to disable the F3 button above
                Yes, and Yes. There is a Field property to disable the RIGHT-Click button. you have to set the property for all of the fields. you will not see the right-click menu at all. Note; It will works with the Form Property restriction.

                Comment

                Working...
                X