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



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

Runtime - Change Mode

  • Filter
  • Time
  • Show
Clear All
new posts

  • Runtime - Change Mode

    I am currently converting an application from v10 to v11 and have hit upon a difference that is causing me problems. In v10 it was possible to allow changes in an embedded browse by unclicking the 'Change Record' property of the browse allowing runtime users the ability to make changes without additional keyboard entries or mouse clicks. In v11 however this setting is ignored in the runtime version and even though the 'Change Record' property has been set to off in the browse the user has to right click on the field to be changed and then select Change Record or press F3. This wasn't the case in v10 and is a functionality that I need to retain in the v11 version. I have tried using the <browse>.change_mode() command in the OnFetch event but this does not work satisfactorily. Can anyone advise how best to achieve this?

  • #2
    Re: Runtime - Change Mode

    <browse>.change_mode() puts a browse in change mode, per the documentation.

    Perhaps you want :BrowseName.restrict_change= .T.

    Or maybe I'm misreading the question. I can't tell whether you are wanting to allow the user to freely change records or to restrict changes.
    There can be only one.


    • #3
      Re: Runtime - Change Mode

      I want to allow changes. In which event of the browse would you suggest issuing the change_mode()? Using it in OnFetch has undesired results.


      • #4
        Re: Runtime - Change Mode


        I don't recall seeing this behavior before unless I've set the form's data entry style to MODAL. Is that what you've done?

        If so, I'd use the OnArrive event in the browse to permit changes, and the OnDepart event of the browse to restrict changes.

        If this doesn't achieve the result you want, post a sample database here with instructions for us to follow in order to see the problem while running your database on our systems.


        • #5
          Re: Runtime - Change Mode

          I've shelved the idea of using "<browse>.change_mode()" as it causes problems with a conditional object that I have on the form. I have tried out "this.allow_change(.T.)" in the OnFetch event of the browse and have the result in runtime that every other row that I click is open for change. I have attached a sample database containing a form with an embedded browse. If you open this form and click on 'Reason' you will see that this is a drop down field. You will also note that when moving to another row this row will be greyed out and not available for change, whereas the next row selected will be changeable. This is an odd behaviour that I hope you may be able to find a solution for.
          Attached Files


          • #6
            Re: Runtime - Change Mode

            I'm not certain that I'm seeing the same behavior you describe. Do you see the same when using the default browse for the set?

            When I switched to modal data entry I see what you mean. Tom has the right idea. Switch to modeless and see if that does what you want.

            View menu, Settings, Data Entry

            There can be only one.


            • #7
              Re: Runtime - Change Mode

              The behaviour I am describing is only visible when opening the form in the runtime version. The form is already a modeless form. I haven't looked at the default browse as this is not what the user will see.
              The issue I have is that users must be able to enter into a field on the browse in runtime without having to press F3 or click and Select Change and this does not seem possible in v11 although my v10 version works as required.
              Thaks for your help.


              • #8
                Re: Runtime - Change Mode

                Thanks. I see now that Modeless isn't default. An easy solution to my problem.