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

Named Browse Bug

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

    Named Browse Bug

    Create two different simple "Named Browses" based on the same table as quickly as you can.... (give each one a different short name)
    At first I thought this was possibly the result of creating one browse and then duplicating it. This is not the case. You can build each independently (without duplicating the first one.)
    To shake things up, you can make changes to one of the browses and this issue still exists. It seems that a5 is "internally transposing the pointers", pointing to these browse objects.

    Watch this short video: http://screencast.com/t/sJW6mb4evx

    BUG: Open (run) two different browses based on the same table or set. After going between the two several times, switch one to edit mode using the toolbar. Once you do this, you're left with two instances of the same browse on the screen. (The XBE confirms this.)

    After opening these browses in view mode, notice what happens to the names of the browses when one is switched from view to edit mode. (and look at the browse object names in the XBE)
    (To make this happen repeatedly, all you have to do is click back and forth a few times between the two browses and then switch one of them into edit mode.)

    I don't know whether this problem exists in v.12 also, but I'd be willing to bet it does. I will test this when I finally get around to installing v.12.....
    FYI: I can can recreate this problem over and over again using the most recent v.11 nightly build. (using any tables or set)

    Although this "anomaly" was uncovered during the development cycle, who's to say that it can't/won't/doesn't have deeper implications?
    Regardless, the mere notion that opened objects can become "mixed up/transposed" (this easily) is not comforting.
    Last edited by SNusa; 01-06-2014, 02:07 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."
    Tags: None
    #2
    Re: Named Browse Bug

    Make changes to BrsOne in the design mode, save, close then re-open both browses, see if the changes stick.

    Comment

      #3
      Re: Named Browse Bug

      Originally posted by G Gabriel View Post
      Make changes to BrsOne in the design mode, save, close then re-open both browses, see if the changes stick.
      Yep, still an issue after adding a filter to _brsONE. Also, after removing a column to _brsTWO same thing is still happening. (XBE confirms it. Setting IW session does too.) I believe you can make as many changes as you like to either of the two browses and this will continue to happen as long as both browses are based on the same table (or set.)

      FYI: I've been able to successfully get the HTML editor to work in v.11 with IE11 installed.
      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: Named Browse Bug

        Did the changes stick to the correct browse?
        IOW, if you open BrsOne in design mode, and the name changes to BrsTwo but nonetheless you go ahead and make some changes (for instance change a column title) save, close re-open BrsOne. Did the changes stick?

        Comment

          #5
          Re: Named Browse Bug

          Originally posted by G Gabriel View Post
          Did the changes stick to the correct browse?
          IOW, if you open BrsOne in design mode, and the name changes to BrsTwo but nonetheless you go ahead and make some changes (for instance change a column title) save, close re-open BrsOne. Did the changes stick?
          Oh yeah, the changes (made to the second instance of the browse (_brsTWO0) do get applied to _brsTWO.
          And this issue is also occurring in v.12. Bill Griffin confirmed it on his own set of data.
          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: Named Browse Bug

            Robert:
            That's not what I asked. I asked if it applied to BrsOne? (the one that took on the wrong name in Design mode)

            Comment

              #7
              Re: Named Browse Bug

              Originally posted by G Gabriel View Post
              Robert:
              That's not what I asked. I asked if it applied to BrsOne? (the one that took on the wrong name in Design mode)
              No, _brsONE remains "untouched." ~ The changes (on the object that "took the wrong name (_brsTWO0) do get applied to _brsTWO)
              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

                #8
                Re: Named Browse Bug

                Report as a bug.

                Comment

                  #9
                  Re: Named Browse Bug

                  Originally posted by G Gabriel View Post
                  Report as a bug.
                  I'll report it, but (given it's a classic desktop related bug) do you think it has a reasonable chance of getting fixed? (Given the fact that the problem extends to v.12 too?)
                  When I do, I'm going to ask them about the other bugs too (which were never acknowledged.) ~ I just read on another thread that Alpha was "completely out of the desktop market."

                  Maybe this assessment is true, but I just can't believe that doing so really makes any sense. Not until windows gives the desktop up completely. And that's not happening anytime soon. Especially with the desktop features that were added back into Windows 8.1 as a result of user dissatisfaction. IMO, just like the .com boom went bust in the late 90's (which came back), so will the desktop. (Although IMO it really hasn't gone anywhere. Everyone is just "playing make-believe" for the sake of selling something new!)

                  I should probably install v.12 first (which I haven't as of yet), to provide build info etc. Otherwise I suspect the report may literally end up in the trash....
                  Last edited by SNusa; 01-06-2014, 04:39 PM.
                  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

                    #10
                    Re: Named Browse Bug

                    They do fix the bugs. I had no issues with the alpha folks responding promptly. I can't report since I do not have your version.
                    In the meantime, open brsTwo first, then open BrsOne second. Repeat the same process in this case put BrsTwo in design mode and see what happens.

                    Comment

                      #11
                      Re: Named Browse Bug

                      Originally posted by G Gabriel View Post
                      They do fix the bugs. I had no issues with the alpha folks responding promptly. I can't report since I do not have your version.
                      In the meantime, open brsTwo first, then open BrsOne second. Repeat the same process in this case put BrsTwo in design mode and see what happens.
                      Doing this leaves two instances of _brsONE. ( _brsONE and _brsONE0 )

                      Snap 2014-01-06 at 19.43.08.png
                      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

                        #12
                        Re: Named Browse Bug

                        Evidently alpha is pointing to the last browse opened to that table. That will help the alpha folks resolve the issue.

                        Comment

                          #13
                          Re: Named Browse Bug

                          I was under the impression that V11 was not going to have any more development or fixes?
                          What is Alphas general response to bugs like this on the desktop side?

                          Comment

                          Previous template Next
                          Working...
                          X