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

V11 browse problem

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

    V11 browse problem

    I have a customer with problem with browses, fishing for suggestions.

    They have a lot of browses in forms - often used as navigational components.

    When a change is made to some field/value outside the browse but on the form, and the record committed, the browse changes its display of records and appears to duplicate at least one of the records.

    Example:

    Browse records are:
    ABC
    DEF
    HIJ

    User selects the DEF record, does something with it, commits, and the browse now displays:

    ABC
    ABC
    HIJ

    This does not happen in their app when they use V10. Only when they use V11, both in runtime and developer's copies.

    It does not happen when I run it in my V11.

    We tried turning off their antivirus, no difference.

    I've tried a lot of Xbasic methods to force the browse to refresh after a parent record commit: refresh(), resynch() and the several variations, but with no effect.

    So, outta ideas, suggestion box is now open.
    -Steve
    sigpic

    #2
    Re: V11 browse problem

    Steve, I have described a problem that reflects this in a few threads. And it is not consistent in that when it is going wrong it almost always does, when you find something that seems to resolve it it works, for a while. I've resolved them when they occur by eliminating some of the commonality;-
    The phenomenon is typified by the the record being operated on reflecting a field value from the first record (topmost in the browse).
    Form calc fields and/or table rules and/or browse calcs seem to conflict, especially when also using table event events.
    With some calculations browse wide (calcs across all children in the browse).
    Anything sound similar in yours?

    Comment


      #3
      Re: V11 browse problem

      Steve,

      Suggest you test behavior using the Alpha Five "default form" for your set. If that works correctly you may safely conclude the problem is not in field rules, but lies instead in your custom form.

      Is the customer using a runtime that's a different "build" from the developer version used to create the form?

      Was the form originally created in versioin 10? If so, does the problem disappear if you duplicate (or recreate) the form in vers 11?

      Is their system running out of resources? i.e. are they multi-tasking other large apps?

      -- tom

      Comment


        #4
        Re: V11 browse problem

        You might also want to check whether the browses that cause this are actually on tabbed objects. Multiple browses layered on various tabs in the same position are sometimes causing such problems.

        Comment


          #5
          Re: V11 browse problem

          I'll add the question -
          If you were to use a dialog to present the table fields and values, make a value changes in the dialog and then write the changes to the table directly using table.get("tablename"), does the problem manifest/persist?
          Mike W
          __________________________
          "I rebel in at least small things to express to the world that I have not completely surrendered"

          Comment


            #6
            Re: V11 browse problem

            Thanks all, I've passed this thread along to customer. Marcel - you probably called it. These are huge complicated forms with tabs, conditional objects - you name it. Designed by someone else, inherited by me - I never would have built it quite like this. But the big puzzle is that it worked in V10 OK, works on my V11 but not any of customer's V11 installations.
            -Steve
            sigpic

            Comment


              #7
              Re: V11 browse problem

              A butterfly effect from some minor shift in some register in one version change. The answer is like looking for a quantum particle in a haystack.

              Comment


                #8
                Re: V11 browse problem

                Have a look here, Steve... and at the video link included in the message. I solved my problem... the browse is now solid. See if it has anything to do with your issue.

                http://msgboard.alphasoftware.com/al...ds-from-Xbasic

                Comment


                  #9
                  Re: V11 browse problem

                  Steve,

                  I was able to recreate this browse issue every time.
                  I submitted a bug report.
                  The Feb 4 pre-release has the fix.
                  I've been testing and it looks good so far.

                  Ron
                  Alpha 5 Version 11
                  AA Build 2999, Build 4269, Current Build
                  DBF's and MySql
                  Desktop, Web on the Desktop and WEB

                  Ron Anusiewicz

                  Comment


                    #10
                    Re: V11 browse problem

                    I have a very similar situation.
                    The error you can get is different, and is related only to the second level child fields inside the browse.
                    But many thing are similar: browse inside a conditional object, calculated fields, etc.
                    If you want to check:
                    http://msgboard.alphasoftware.com/al...eld-any-advice
                    So I'm waiting to try the fix, I will keep you up to date.
                    Bye!

                    Comment


                      #11
                      Re: V11 browse problem

                      Steve, are the form and browse tables native Alpha or Linked?

                      I had a problem with Active Linked tables and browses. The Active Linked tables were Access tables. The browse is extremely simple. All the work I was doing against the browse was in code. I had three basic problems: 1. Delete a browse record. 2. Add a record to the browse. 3. Re-sort the browse records. The problems were always an appearance of duplicate records - the browse just looked like there were duplicates... but in fact, there were not. Or, browse records disappeared completely - they were there... just not shown. Moving to another parent record would display the parent record information, but not the browse information... sometimes... other times everything would be in sync... it seemed quite random.

                      As soon as I solved one issue with various serverside refreshes, refreshes, resynces... using cursors in code, etc., one of the other 2 solved issues would pop up again. I was going round and round for about 2 weeks. Then I solved it. In a hour I created an import routine and moved everything to native dbf tables. All problems gone.

                      Using cursors in code was a huge help... it did solve many issues I was having. All this was under Version 11. None of this helps you, but thought I'd throw it in anyway.

                      Comment

                      Working...
                      X