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

Filtered lookup

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

    Filtered lookup

    In an embedded browse, I have created a filtered look up. There are 2 fields CleintID and SessionID. Once the ClientId field is filled in, the SessionId field's look up is filtered on the ClientID. If the clientID field is changed to another client. I need the SessionID field to be set to "blank". I tried field rules, default with an expression but can't get it to work. I also can't find a way to do it on the browse itself, with an event.

    #2
    Re: Filtered lookup

    I would try using an onChange event function. If the mode of the browse is CHANGE then blank the SessionID field. If the mode is ENTER then don't do anything.

    Comment


      #3
      Re: Filtered lookup

      Tom,
      Let me try another approach to this problem. What Im trying to accomplish is to insure that the sessionID (which is not always filled in) is a session that belongs to that client. How can I setup validations in field rules insure that?

      Comment


        #4
        Re: Filtered lookup

        I don't think you can do this in field rules.

        The value in the sessionID field is dependent on two things: (a) the value in the clientID field; and (b) the sessionID the user picks from the filtered lookup.

        Comment


          #5
          Re: Filtered lookup

          What would be the correct approach?

          Comment


            #6
            Re: Filtered lookup

            What's wrong with Post #2, above?

            Comment


              #7
              Re: Filtered lookup

              Will try to figure it out. Thanks

              Comment


                #8
                Re: Filtered lookup

                Check the OnChange event in the section on Events for Browse objects here.

                Comment


                  #9
                  Re: Filtered lookup

                  Can you explain a bit more please Baz?
                  What you seem to be saying is that you want to;
                  Select a Client ID and this shows the options for the Session ID from the lookup.
                  If the Client ID changes, the Session ID is set to Blank?

                  If you are using a lookup, then changing Client ID will automatically result in the presentation of the corresponding Session ID.

                  One way around this is to NOT trigger the second filtered lookup using OnChange as Tom suggests.
                  What do you want to happen if the user deletes the content of the Client ID field entirely?

                  An example of where you have gotten to would help - for this and the other syntax post.
                  See our Hybrid Option here;
                  https://hybridapps.example-software.com/


                  Apologies to anyone I haven't managed to upset yet.
                  You are held in a queue and I will get to you soon.

                  Comment


                    #10
                    Re: Filtered lookup

                    What I'm trying to accomplish is to insure that when a client id is entered, that the session id that is selected can only be a session that belongs to that client (it is selected from a table called sessions). The filtered look up on the session id field works. However If the client ID field is either blanked out or changed after a valid session id has been entered, I don't know how to enforce that the session id still belongs to that client. I tried some expressions in field rules cross validation on the session Id field, but could not get it to work.
                    calendar.png

                    Comment


                      #11
                      Re: Filtered lookup

                      Try this. The syntax might not be 100% BTW
                      Create an Index using both the Client ID and Session ID
                      trim(client_id)+trim(session-id)
                      Use EXIST() to see if there is a valid match in the OnChange event, using the value of the changed/blank field plus the value of the sesion id.

                      The easiest way would be to prevent any changes to the Client ID is there is a valid session present.
                      To change the Client ID, the record - including any Session ID should be deleted and reentered.
                      See our Hybrid Option here;
                      https://hybridapps.example-software.com/


                      Apologies to anyone I haven't managed to upset yet.
                      You are held in a queue and I will get to you soon.

                      Comment


                        #12
                        Re: Filtered lookup

                        Thanks Ted,

                        Tom Cone was kind enough to help me out with this last night. The following code was attached to the Browses Events, Event.

                        Code:
                        FUNCTION CLIENT_iD_onChange as v ()
                        	:Appointments:Control_browse1:Session_id.Text = ""
                        	end function
                        This blanks out the Session ID field if the Client ID is either changed or emptied.

                        Comment

                        Working...
                        X