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

Strange Form/Browse behaviour

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

    Strange Form/Browse behaviour

    I have a form that displays a browse.
    The form is based on a single table.

    The browse has a ProductNumber field and a Quantity field.

    I have entered the following short script on the OnRowDblClick action:
    'Allow editing of records in current form at parent level.
    topparent.allow_change(.t.)

    'Change record in current form at Browse1 level.
    topparent:Browse1.allow_change(.t.)

    'Mark record in current form at parent level.
    topparent:Browse1.mark_record()

    'Activate object 'BROWSE1:Tmpquantity' in current form.
    topparent:BROWSE1:Tmpquantity.activate()

    'Set 'Value' property of 'Browse1:Tmpquantity' in Form 'FrmSelectProductV10' .
    parentform:Browse1:Tmpquantity.value = VarNum3

    'Save record in current form at parent level.
    topparent.commit()

    When I first load the script I set the order to ProductNumber and activate the Quantity field in the first record.

    THE PROBLEM

    If I dblClick a record other than the first record the record is marked BUT the Quantity field in the FIRST record is changed to 1 and the Quantity field in the dblclicked record is left unchanged.

    BUT

    If I continue dblclicking on any other records, all goes as expected.

    So... in other words, no matter which record I dblClick when the form first loads the Quantity record in the first record in the browse gets (incorrectly) changed.
    Subsequent dblclicks on any record (correctly) changes the Quantity value in the record that was dblclicked.

    How can I fix this?
    Last edited by David Boomer; 02-03-2013, 06:09 PM.

    #2
    Re: Strange Form/Browse behaviour

    Check this screencast.

    Comment


      #3
      Re: Strange Form/Browse behaviour

      Originally posted by Tom Cone Jr View Post
      Hi Tom;

      Quick question: What was the reason/significance for setting the form as modal, and then switching form modes back and forth via the AS?
      (I'm thinking I am missing the significance of something here.) ~ Does this form mode change circumvent the embedded browse cursor position problem the OP was experiencing when the browse first gets focus?

      In other words, does setting form mode (from within the embedded browse) essentially accomplish this?: this.Set_Viewport_row(row)

      ~Thanks in advance.
      Last edited by SNusa; 02-04-2013, 12:49 AM.
      Robert T. ~ "I enjoy manipulating data... just not my data."
      It's all about the "framework." (I suppose an "a5-induced" hard drive crash is now in order?)
      RELOADED: My current posting activity here merely represents a "Momentary Lapse Of Reason."

      Comment


        #4
        Re: Strange Form/Browse behaviour

        Robert, David's code used the "allow_change()" method. This is usually necessary only when the form is MODAL. So, I inferred that his form was MODAL, hence I did the same thing in order to try to better emulate his exact scenario. I did not toggle MODELESS / MODAL for any other reason and don't know the answers to your questions.

        Comment


          #5
          Re: Strange Form/Browse behaviour

          Thank you Tom.

          The topparent:mark_record() method(in the Mark Record A/S) must be taking care of the following (internally): this.Set_Viewport_row(row)
          I doubt it shows up in the script recorder..... But I'm curious, and will check anyways.

          PS: Your assistance & video presentations on these forums are invaluable!
          Last edited by SNusa; 02-04-2013, 10:26 AM.
          Robert T. ~ "I enjoy manipulating data... just not my data."
          It's all about the "framework." (I suppose an "a5-induced" hard drive crash is now in order?)
          RELOADED: My current posting activity here merely represents a "Momentary Lapse Of Reason."

          Comment


            #6
            Re: Strange Form/Browse behaviour

            Thanks Tom

            This works... I did not realize that the mark record code also commited the record.

            Comment

            Working...
            X