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

Strange Control Browse Issue

  • Filter
  • Time
  • Show
Clear All
new posts

    Re: Strange Control Browse Issue

    Thanks to all. The patch fixed the problem.


      Re: Strange Control Browse Issue

      Thanks Tom for your follow up.

      Any idea as to when the pre-release will go into production?


        Re: Strange Control Browse Issue

        Nope, sorry.


          Re: Strange Control Browse Issue

          Originally posted by Ray in Capetown View Post
          This is similar to many reported user experiences with interactive browses.
          Its kind of known about (I don't mean acceptable)

          but often manageable if you have the need. Some methods I have used to tame..

          causes could be;
          Certain OnRow... activity and especially event/events if you use them.
          Table or Form wide calculated fields.
          These may scroll the underlying table and not always re-position the browse. Especially when it is a scrollable browse (ie not all rows fit in the frame)

          try some functions including

          24 May 2013 Raymond Lyons suggested in a post
          "Have you tried <OBJECT>.REFRESH_FIELDS() ? Or <OBJECT>.REFRESH_LAYOUT() with the object being the name of the form?"
          Hi Ray,
          I found a couple of threads that suggested using get_viewport_row() but the problem with that function is that the row number it gets only relates to the rows currently displayed in the embedded browse. IOW you may have 200 records but only 20 display at a time in the browse and so your row number will be in the range of 1-20. If for example you delete a record using the delete_record() function, it will jump to the end of the browse so that scroll_current_row(var) returns you to the row in THAT current display (ie. row 1 is now 20 records from the bottom) - not the one you were viewing before!

          This works in a button for deleting a record then takes you back to the next record in the original display based on my current index key for the form:

          dim gokey as c
          dim curkey as c
          curkey = cdate(txdate.value)+needle.value
          gokey = cdate(txdate.value)+needle.value
          [COLOR="#0000FF"]'used to test
          response = ui_msg_box("Delete Record","Index Key: "+curkey,33)
          if response = 2 then
          end if[/COLOR]

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


            Re: Strange Control Browse Issue

            Yes Robin, I can see how that sequence would keep things tight. Working outside the browse - ie the button is on the parent form.
            Through it, I just discovered another nicety that I hadn't come across, UI_Freeze.
            So if I want a size 36 top there's a high likelihood I'll get one ? (blue is good).

            Could a method like that help in the case of editing directly in a browse where the underlying record (and therefore data) goes out of sync and messes with the current?


              Re: Strange Control Browse Issue

              I've had this issue for years, and not just with embedded browses, but also with the parent record in a set for the form. My approach, where the event and script vary according to the circumstance, has been this:

              In the autoexec I define a global variable
              dim global rnum as n=0

              then, where I am committing a record in the form, I say something like this: (which in this case applies only when editing a record)

              dim global rnum as n
              if t.recno() <> var->rnum
              end if

              where this goes, and the syntax, varies on the situation, but it has been a satisfactory solution for jumping records.
              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


                Re: Strange Control Browse Issue

                If the "commit()" changed the record pointer, then "if t.recno() <> var->rnum" it will be returned to the record visible prior, using rnum.

                My fear with browses is that the edit was made in , say browse line 5, the calculation picked up data from browse line1*. Commit would save the record at browse line 5 (with an incorrect value) and then your test would return one to the same browse line, line5. Which it never left in the first place.

                *this is the most common experience I have had, before I avoided form calcs on browse line fields where some or other form calc parsed the browse records.

                The difficulty is then replicating the scenario for publishing here, in so doing the thing works correctly.
                Going back to the live db and trying to eliminate various things, it begins also to work properly. Sometimes for a while. Then seems to stabilize.
                Now since I am still using v10 I can't very well present a case, if I did nail one example down to being replicable.

                Previously, when it has done that, I have done a check for the record number browse to table, it checks always - but still, a field value from a linked child table is returned with a value from a record that the first item in the browse is linked to.

                I appreciate your interest any how, but wouldn't throw any further effort at it unless you have had some similar experience already. I am circumventing this happening with some avoidance tactics.
                Last edited by Ray in Capetown; 06-15-2013, 10:03 AM.