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

Incorrect results from a Query

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

  • Incorrect results from a Query

    I have a query which searches for the word [ALL] in a record called [LINE_TYPE]. The options are ALL, AP, GL, TX for
    In the result list when the default browse is shown that is exactly what I get.

    When run from a Form with a Browse embedded, I get ONE record with [AP] in it.
    See our Hybrid Option here;
    https://hybridapps.example-software.com/


    There are 3 things you can do in any situation;
    Live with it, Change it or Walk away from it.

  • #2
    Re: Incorrect results from a Query

    Sample database so we can see what you're talking about?
    There can be only one.

    Comment


    • #3
      Re: Incorrect results from a Query

      Originally posted by Stan Mathews View Post
      Sample database so we can see what you're talking about?
      Will do Stan but over the weekend.
      Working long days atvthe mo.
      See our Hybrid Option here;
      https://hybridapps.example-software.com/


      There are 3 things you can do in any situation;
      Live with it, Change it or Walk away from it.

      Comment


      • #4
        Re: Incorrect results from a Query

        when getting a field into a variable?? If a browse has a field named "tomsid" in it and you try to read the field elsewhere on a form named "tomsid", alpha will default to the one in the browse. You can get wrong information. My rule of thumbe is to rename fields in a browse to namebrowse. Alpha seems not to see it at that point. The problem in the browse is that alpha only picks up the data in the first browse record.

        Not sure that has anything to do with your query, but just in case.

        I spent 3 days chasing this same issue. I was getting a number that was different than the focused on record. 683257 instead of the needed 683261.
        Dave Mason
        [email protected]
        Skype is dave.mason46

        Comment


        • #5
          Re: Incorrect results from a Query

          If a browse has a field named "tomsid" in it and you try to read the field elsewhere on a form named "tomsid", alpha will default to the one in the browse.
          Not my experience at all. The only method I know to read a field on a form is to reference the value property of the form object. The browse field will always have a different address than the field object directly on the form.

          formname:fieldobjectname.value

          vs

          formname:browseobjectname:fieldobjectname.value

          If you use incomplete addressing

          fieldobjectname.value

          Alpha will search "up the path", meaning that code using incomplete addressing attached to a browse event will reference the browse field because it will encounter the fieldobjecname before it leaves the browse.

          Code using incomplete addressing attached to a form event will reference the form field because it will encounter the fieldobjecname on the form. Form level code using incomplete addressing should never descend into the browse even if it doesn't find the fieldobjecname used in the code.

          As you've discovered, changing the objectname is one workaround. Using at least relative addressing is safer and leaves no ambiguity.
          There can be only one.

          Comment


          • #6
            Re: Incorrect results from a Query

            I simply changed the object name in the browse, once done the variable was read from the form proper,.

            it is taken care of, but was definitely reading the browse first. I don't know why.
            Dave Mason
            [email protected]
            Skype is dave.mason46

            Comment


            • #7
              Re: Incorrect results from a Query

              the variable was read from the form proper
              Not a clue what you mean.
              There can be only one.

              Comment


              • #8
                Re: Incorrect results from a Query

                I guess I was not clear. Sorry 'bout that.
                Code:
                vinspectidnew = parentform:Inspectid.value works since it reads from the form
                but
                vinspectidnew = parentform:browse1:Inspectid.value 
                
                get the wrong value unless the first record is the one you want.
                
                remove "browse1:"  from vinspectidnew = parentform:browse1:Inspectid.value and the variable still gets populated as before even though the field was on the form outside the browse..
                Option was to change the browse1 field header to something else.
                It was like alpha was looking at the browse even though it was not asked for.
                Dave Mason
                [email protected]
                Skype is dave.mason46

                Comment

                Working...
                X