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

control lookup events

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

    control lookup events

    Hi everyone,

    I have a control that uses an edit-combo lookup linked to a customer table.
    I am trying to force the end user to search for an existing customer before
    being able to enter a new customer.

    The problem I am running into is there does not seem to be an after-selection
    event that allows for a non-selection (escape pressed) or a not-found option.

    I've tried placing something in the onBlur event, but this fires when the lookup
    begins.

    Does anyone know of a workaround ?

    Thanks in advance,

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

    #2
    Re: control lookup events

    In the absence of an event, I wonder if some other method might help "train" the user? How about a validation rule using the Cross-file Validation feature?

    Another thought is that there may be some way to trigger a value driving a show/hide of some control; they would have to go through that event's hoop before they can enter a new customer.
    -Steve
    sigpic

    Comment


      #3
      Re: control lookup events

      Hi Steve,

      This is part of what I'm running into.
      I have the code
      Code:
      var pucus = {dialog.Object}.getValue('PICKUP_NAME');
      var puadd = {dialog.Object}.getValue('PICKUP_ADDRESS');
      alert('Focus has been blurred '+ pucus+' '+puadd);
      attached to the onBlur event, but the onBlur event fires before
      the lookup has a chance to fillin the extra fields.

      If I can get the onBlur event to fire after the fillin is complete,
      or some work-around, I think I can then code either a popup
      window to add a new location, or a button to open a window
      to add a new location.

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

      Comment


        #4
        Re: control lookup events

        How about an if{ statement in your javascript?

        If pucus + puaadd is blank, don't do anything.

        Add a choice to your popup to "Add new" or something like that, and if "Add New" then you can branch as you wish.
        -Steve
        sigpic

        Comment


          #5
          Re: control lookup events

          Attached to what ?

          I want them to start typing the customer name,
          If its not there, or they don't find the right one,
          then they should get the option to put in a new one.
          Gregg
          https://paiza.io is a great site to test and share sql code

          Comment


            #6
            Re: control lookup events

            I've pondered this for a long, long time. It appears to me that since there is a lookup, there ought to be a way for the user to add the data to the lookup table. As I'm typing this, I got the idea of placing a button on the bottom of the grid which the user can use to open the lookup table, enter the data and when the data is saved and the lookup table is closed, the newly entered data appears in the grid. Obviously haven't looked into this yet but that is one way I think it could be done.
            TYVM :) kenn

            Knowing what you can achieve will not become reality until you imagine and explore.

            Comment


              #7
              Re: control lookup events

              I want the option to add a new record to be available only if they are unable to find
              what they are looking for.

              I know we have the AfterSelect event, but I need something to work like AfterNoSelect
              to make the add record option visible.
              Gregg
              https://paiza.io is a great site to test and share sql code

              Comment


                #8
                Re: control lookup events

                My suggestion is a work around but probably not an easy one when it comes to the last part of it. Yes, I agree with you. This is one of those things that, IMHO, Alpha has got it only half done. There needs to be a property in the lookup that allows the user to add a new record to the lookup. Something like, tic a box that says, User can add new record to lookup table if no lookup is found. That would then show additional properties which would path to the lookup table, etc. It would place a button on the grid that when pressed, opens the lookup table. When the data is saved, and the lookup table is closed, the new data appears in the grid.

                Maybe you or others have a better idea on how to do this.
                TYVM :) kenn

                Knowing what you can achieve will not become reality until you imagine and explore.

                Comment


                  #9
                  Re: control lookup events

                  I knew if I went to sleep often enough with this problem not being solved, the answer would come to me in my dreams.

                  I created a button to open a dialog to add a new record.

                  In the client-side show/hide expression, I used the code : pickup_name !='' and pickup_address = ''
                  Gregg
                  https://paiza.io is a great site to test and share sql code

                  Comment


                    #10
                    Re: control lookup events

                    Originally posted by madtowng View Post
                    I knew if I went to sleep often enough with this problem not being solved, the answer would come to me in my dreams.

                    I created a button to open a dialog to add a new record.

                    In the client-side show/hide expression, I used the code : pickup_name !='' and pickup_address = ''
                    After the new record is submitted, does it populate the grid with the new record as outlined in my suggestion or do you do a lookup?
                    TYVM :) kenn

                    Knowing what you can achieve will not become reality until you imagine and explore.

                    Comment


                      #11
                      Re: control lookup events

                      I don't have that part of the new dialog completed yet.
                      I'm still trying to think of a way to get what was typed into the name
                      control to show up in the name control on the pop-up dialog.
                      Gregg
                      https://paiza.io is a great site to test and share sql code

                      Comment

                      Working...
                      X