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

Lookup works in Ver8 but not Ver9

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

  • Lookup works in Ver8 but not Ver9

    In the attached database, the "fill-in" feature from a look table works in Ver 8 but does not work in Ver 9. Open form "Price_History_Worksheet" and add a new record (F3) to the upper browse. The "CATAGORY" field references a look-up list from a separate table.

    Upon entry of a character (select V for Valve), the look-up selectes its best match to select the correct entry value (VALVE) from the list and highlights it. In Ver 8, if you then hit the enter key, the highlighted value would be entered and the cursor moved on to the next field. In Ver 9, only the letter you initially input is entered and accepted. If you click on the down arrow, open the list and click on the hightighted value, it is then entered properly.

    The same thing happens in the lower browse. "Source" is selected from another table in the same manner with the same results. Except here an error message is displayed because of configuration selections I have made.

    Both of these features worked correctly in Ver8. In Ver 9, is this a bug or is this a result of some other "improvement" and I now need to add extra code?

  • #2
    Re: Lookup works in Ver8 but not Ver9

    I didn't try your zip, but I think you should submit this as a bug. I have a user who periodically has the same problem with V8. And I have seen the behavior while logged on remotely.

    When/where it occurs, you have to use the mouse, which can be aggravating for users.
    Cole Custom Programming - Terrell, Texas
    972 524 8714
    [email protected]

    ____________________
    "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

    Comment


    • #3
      Re: Lookup works in Ver8 but not Ver9

      your field rules "allow any value", and you have several entries in the lookup with the same first letter. Make your rules for the lookup to "pop up on mismatch"

      Comment


      • #4
        Re: Lookup works in Ver8 but not Ver9

        In your field rules for Description.dbf in your lookup for vendor you have "Force Closest match", but in the Category field you have "allow any value", so the v you are putting in is any value and it allows it. If you want to accept the lookup use the right arrow to move to the next field instead of tab. Or change the field rule to "Force Closest Match".

        PS Since I do not know where you are from, I will assume the US and the proper spelling for Catagory is Category.
        Bill Griffin
        Parkell, Inc

        Comment


        • #5
          Re: Lookup works in Ver8 but not Ver9

          Originally posted by Bill Griffin View Post
          PS Since I do not know where you are from, I will assume the US and the proper spelling for Catagory is Category.

          Oh man! If we start correcting typos on this board, we'll be here all day!
          Peter
          AlphaBase Solutions, LLC

          [email protected]
          https://www.alphabasesolutions.com


          Comment


          • #6
            Re: Lookup works in Ver8 but not Ver9

            Peter,

            Was not correcting his typo on the board (I could care less about spelling, since I am guilty of more than my fair share of misspelled words), but in the application. Not usually to cool to have an application that has misspelled words or terms in it. (I know from experience)

            Bill
            Bill Griffin
            Parkell, Inc

            Comment


            • #7
              Re: Lookup works in Ver8 but not Ver9

              Ok, got it. Good point.
              Peter
              AlphaBase Solutions, LLC

              [email protected]
              https://www.alphabasesolutions.com


              Comment


              • #8
                Re: Lookup works in Ver8 but not Ver9

                Tank you all for your replies and I will look at your suggestions - but - the point is that if I open this application in Version 8 it works, it does not in Version 9. And yes, even in Michigan, the correct spelling is "category".

                Comment


                • #9
                  Re: Lookup works in Ver8 but not Ver9

                  I am not on my computer with alpha5, so I can not look at the file, but this sounds like the same problem I had.

                  I assume you are using a variable to perform the lookup.

                  Look at the xbasic code of your script, I think you will find something similar to : auto_list_qsku = table.external_record_content_get("invitems","Sku","Sku","Customer_id = Var->qcustid")

                  This fails under version 9. There is a s_quote command that makes this work.


                  auto_list_qsku = table.external_record_content_get("invitems","Sku","Sku","Customer_id = " + s_quote(qcustid))

                  I converted the code to inline xbasic code to make my script work immediately.

                  Selwyns Rabins gave me this fix, and is aware of the bug.
                  He said it would be fixed in the next update.


                  I hope this helps you.

                  Gregg
                  Gregg
                  https://paiza.io is a great site to test and share sql code

                  Comment


                  • #10
                    Re: Lookup works in Ver8 but not Ver9

                    Gregg,

                    Sorry for the long deleyed reply, been on vacation. Thanks for the fix, I will try it out.

                    Tim

                    Comment

                    Working...
                    X