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

Lost Query - Bug or Expected

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

    #16
    Re: Lost Query - Bug or Expected

    Donald

    Had a look at your sample attached to the other post.

    I would say what you are experiencing is not a bug.

    When the form first opens, the base filter on the form is activated and Shippingticketno 4 is shown as it should be.

    If at that time you load the companion browse you will see that the order is 4 3 2 1.

    Now when you go back to the form, and then enter a new record and then cancel it, the form now shows shippingticketno 1 which is the last record by filter in the table. When you cancel it goes to the last record which is shippingticketno 1.

    If you change the base filter to ascending and open the form - shippingticketno 1 will be shown based on the filter. Enter a new record and then cancel, then the last record in the filter will be shown which is shippingticket no 4 - which is what happens.

    Now back to the invert(shippingticketno) as the base filter, if you use query by form and say select shippingticketno 3. That will be shown on the form, then if you call the companion browse it will only show the result of the query which is shipping ticket No 3. Just as it should. Now when you switch back to the form it again will load to the query which is shippingtickeno 3.

    It seems to be working as it should.

    FWIW
    Tom

    Comment


      #17
      Re: Lost Query - Bug or Expected

      Tom,

      Thanks so much for your reply.

      In you last paragragh, if you go back to the browse and back to the form again, the query does not hold. Can you go back and forth between the form and the browse, say a few times, and the query stays put?

      Comment


        #18
        Re: Lost Query - Bug or Expected

        Donald

        I now see what you were seeing. When you QBF and say select 3, then go to the companion browse, it shows 3 and only 3 - then return to the form and then go back to the companion browse and it shows all - the query did not hold

        I tried it in Version 8 and Version 9 and the query does hold.

        I would suggest that you send this in as a bug using your sample program and see what Alpha has to say about it

        Tom
        Last edited by Tbaker; 01-21-2011, 02:20 PM.

        Comment


          #19
          Re: Lost Query - Bug or Expected

          Tom,

          I suspect if you go into V8 or V9 and try to enter a record and then immediately cancel it you will remain on the current record (shipping ticket 4).

          If you want to play with it further, as I said before, if you change the sort order on the form to ticket number ascending, all problems go away. Something is up with the form when descending order is set.

          I am glad someone sees what I have been experiencing, I have killed days working on this issue. Is it difficult to submit a bug report? Do you know if they looked at with any urgency?

          Thanks again, Don

          Comment


            #20
            Re: Lost Query - Bug or Expected

            Originally posted by DORaymond View Post
            Tom,
            Is it difficult to submit a bug report? Do you know if they looked at with any urgency?

            Thanks again, Don
            Got to Help menu on top, go down to "send a bug report"

            Give them description of problem & how to recreate it. Also send them your form & DB. Sometimes I get answer in day, a time or two I was showed a work around or how to correct my programing. I think once I never heard back on.

            Comment


              #21
              Re: Lost Query - Bug or Expected

              Don

              You are right about the record holding in Version 8 and Version 9 when entering a new record then cancelling it. The record number that was up at the time of the enter record is still the record you come back to.

              I see Jack has given you instructions on how to send in a bug report.

              Tom

              Comment


                #22
                Re: Lost Query - Bug or Expected

                Well I sent in a bug report, and I think the reply was obvious and does not address the problem. I don't know what to do now - I am stuck.

                Here is Alpha's response:
                Hi Donald,

                The form defines its own query (look at form properties - filter/order
                - there is an order defined) - This order is causing a query to be run when the form is opened. If you remove the form order (both filter &order blank) then the form preserves the order when the F8 key is pressed.

                Thanks,
                Cian Chambliss

                This does not address the issue of the query not holding when toggling between the companion browse and the form, unless he is trying to say that you cannot use a descending sort for the form.

                Comment

                Working...
                X