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
Devcon 2020 Goes Virtual! LEARN MORE >

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

Embedded browse problem

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Embedded browse problem

    I have come across a problem with the embedded browse. Here is the sequence of events:

    1) Select a record (but not the last record), and then delete it using an action script ( e.g. behind a button)

    2) Enter a new record with a field item with the same value that you just deleted (it appears at the bottom of the browse)

    3) Now repeat step 1 (delete it)

    The browse does not refresh properly. The display gets progressively worse at you repeat these steps

    Anyone else seen this, have any ideas? I have a small database that demonstrates this if anyone is interested.
    Tags: None
    #2
    RE: Embedded browse problem

    Have you tried adding a refresh action to the buttons OnPush event?

    Comment

      #3
      RE: Embedded browse problem

      Yes - I built a script attached to button which deletes the record and then refreshes the browse object.

      I've experimented with this a bit further. I tried it with a linked browse and the same thing happens. The problem appears to be related to sorting.

      I have found a fix by adding a quick sort action before the refresh. This seems to work.

      I have this demonstration is a small db if you are interested. I've tried contacting alphasoft, but I cant seem to find anyone who is interested in this issue! - maybe because I am still on the trial version!

      Thanks for your reply! Kevin

      Comment

        #4
        RE: Embedded browse problem

        Zip up the App & post it.

        Comment

          #5
          RE: Embedded browse problem

          Unfortunately, refreshing browses is one of the weak points in Alpha. It can be done but it's often a matter of trial and error to find something that works in specific situations. (If anyone can present some logic of why, or in what situations, some things work and others don't, PLEASE tell us!)

          Getting the data in has always been reliable but getting it to display correctly in 'complex' situations can be difficult. Unfortunately, if the display isn't correct, the user may change the data again thus messing up the results.

          In most cases, the browse works best if you can work directly within it rather than working on the table and refreshing the browse.

          If you need to work on the table, try various combinations of the following commands to refresh the browse.

          parentform.resynch()
          parentform.refresh_layout()
          parentform:browse1.activate()
          parentform:browse1.resynch()
          parentform:browse1.refresh()

          Often a liberal sprinkling of xbasic_wait_for_idle() between each command seems to help.

          Also, in some cases I've resorted to doing a
          parentform.fetch_prev()
          parentform.fetch_next()

          Another thing that worked once was putting a ui_msg_box( "", "" ) somewher in the middle of the 'refresh stuff'. Somehow that seemed to give it the opportunity it needed to finish the refresh. This is a bit annoying if there's no need to prompt the user for/about anything but in that case it was needed anyway.

          And, as I recall, I once closed the whole form and re-opened it using a find() to get to the correct record. Annoying but it worked.

          Cal Locklin
          www.aimsdc.net

          Comment

            #6
            RE: Embedded browse problem

            Here is the zipped db

            Just view the forms, EB Doesnt work and EB works. There are notes on each form

            Kevin

            Comment

              #7
              RE: Embedded browse problem

              Kevin,

              I looked at your example and, as you say, adding quick sort does work.

              I looked at the xbasic version of your action scripting and noticed that you are adding records to a different instance of the child table rather than to the current instance.

              I wonder whether this has something to do with your problems, even though, as Cal notes, there are some valid issues with A5's browse object.

              Bill
              Bill Hanigsberg

              Comment

                #8
                RE: Embedded browse problem

                I converted your plus button's code to xbasic and substituted table.current() for table.open() and the problem went away.

                If you try this remember to eliminate the table.close() line as you cannot close the current table.

                Also, I substituted topparent.resynch() for topparent:browse1.refresh(). I didn't spend a lot of time determining whether this was absolutely necessary but I did note that there were no fields displayed on the form; only the embedded browse.

                As a note to any onlookers, this form is based on a single table rather than a set.

                Bill
                Bill Hanigsberg

                Comment

                Previous template Next
                Working...
                X