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

filtering problems exposed - v6<>v7

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

    filtering problems exposed - v6<>v7

    I was cleaning out some old forum sample applications and came across one that was originally done for v6 and found that it would not work in v7. It was to show how to filter child records. I think the original author was Tom Cone Jr.

    I think this may highlight a couple of the problems that some have been bringing to the v7 forum re filtering. It seems that in some situations if you don't cause the filtered records to be in some sort of order(pardon the pun) either by supplying an order expression or filtering on something other than .t. strange things can happen.

    Two situations are described.
    1. filtering child records using .t. as the filter causes ALL the child records to show rather than only the child records that belong to the parent.
    2. filterng parent records using a child field without specifying an order cause an error of "Invalid filter or order expression"
    The png attached shows the form1 with more explanations so you can see before you buy so to speak.

    If anyone else can confirm this I will submit it as a bug report.
    Tim Kiebert
    Eagle Creek Citrus
    A complex system that does not work is invariably found to have evolved from a simpler system that worked just fine.

    #2
    Re: filtering problems exposed - v6&lt;&gt;v7

    Tim,

    Works exactly as your notes on the form say, tried out in V6 and V7.

    I have begun to notice some filtering problems on one of my forms but thought it was part of the browse glitch, everytime I open a new browse that is filtered on a parent with no child records, there is one child record and the dbsum() calculated field at the base of the form shows a different total. It is always the same child record and always the same figure in dbsum() - 19, which if it was adding the total of the mysterious child record would be 2.5.

    Yes - table has been packed.

    After entering new records into the browse (done via xbasic) the mystery child record disappears and the dbsum() is correct. However if I scroll up through newly entered records, sometimes all child (unfiltered) records are shown!!

    Comment


      #3
      Re: filtering problems exposed - v6&lt;&gt;v7

      Lance,

      Thanks for the confirmation. I will send in a bug report.
      Tim Kiebert
      Eagle Creek Citrus
      A complex system that does not work is invariably found to have evolved from a simpler system that worked just fine.

      Comment


        #4
        Re: filtering problems exposed - v6&lt;&gt;v7

        Tim,
        Yes what you say happens with me also. For completeness sake, though, the scripts I see in your button 2 and 3 are the same and not different as you describe.

        This is a great insight because I have been cursing about this for a yerar now. Thanks for the post!!!

        Mike W
        Mike W
        __________________________
        "I rebel in at least small things to express to the world that I have not completely surrendered"

        Comment


          #5
          Re: filtering problems exposed - v6&lt;&gt;v7

          Here is a repost of my sample with a correction to buttun 4.

          It had (as Mike pointed out) the same code as button 3 :o.

          It now behaves as described in the note beside the button. Some thing I had not noticed before is that once button 4 is used setting a filter and an order expression button 2 then works correctly. Close the form and re-open it and button 2 behaves incorrectly again. Until button 4 is used button 2 causes all child records to show rather than just those related to the parent.
          Tim Kiebert
          Eagle Creek Citrus
          A complex system that does not work is invariably found to have evolved from a simpler system that worked just fine.

          Comment


            #6
            Re: filtering problems exposed - v6&lt;&gt;v7

            Tim, I see the same behavior here and recommend you submit the bug report. These difficulties all involve the <form>.queryrun() method, though they're wrapped in action scripting statements. I suggest that when you submit the bug report you might stress that these problems occur while using action scripting. -- tom

            Comment


              #7
              Re: filtering problems exposed - v6&lt;&gt;v7

              I have submitted the bug report. I will report here if I hear back.
              Tim Kiebert
              Eagle Creek Citrus
              A complex system that does not work is invariably found to have evolved from a simpler system that worked just fine.

              Comment


                #8
                Re: filtering problems exposed - v6&lt;&gt;v7

                Tim, Tom,

                Do you remember this/these threads:

                http://msgboard.alphasoftware.com/al...ad.php?t=63086
                http://msgboard.alphasoftware.com/al...858#post395858.

                I sent a Bug report regarding this in August and heard nothing back. As Tom responded for both, this involves <form>.queryrun() I'm thinking these are related.

                I attached the example DB and a screen shot of the error that I sent in to Alpha as a Bug report.

                Mike W
                Mike W
                __________________________
                "I rebel in at least small things to express to the world that I have not completely surrendered"

                Comment

                Working...
                X