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

Limit Textbox Lookup to an item in the lookup Window

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

    Limit Textbox Lookup to an item in the lookup Window

    That attached zip file contains a 35 second recording of my lookup problem. I hope this is a quick, acceptable way to show my issue.

    I want the Textbox with a Lookup to be limited to just items in the lookup window.

    #2
    Re: Limit Textbox Lookup to an item in the lookup Window

    Hi Ken,

    This question has been asked a lot without any real solution, but I just figured one out...

    You can render any input field readonly with an HTML parameter or javascript. The HTML parameter is READONLY and the javascript is onFocus="this.blur()".

    A normal rendering of a Grid input field in the browser looks like this:

    <input id="V.R1.COMPANY" size="20" maxlength="20" class="SunsetInput" type="text" name="V.R1.COMPANY" value="ACME Construction" />
    <input id="V.R1.COMPANY" size="20" maxlength="20" class="SunsetInput" type="text" name="V.R2.COMPANY" value="IDEAL Maintenance" />
    etc.


    To render it readonly, it should look like this:

    <input id="V.R1.COMPANY" READONLY size="20" maxlength="20" class="SunsetInput" type="text" name="V.R1.COMPANY" value="ACME Construction" />

    or

    <input id="V.R1.COMPANY" onFocus="this.blur()" size="20" maxlength="20" class="SunsetInput" type="text" name="V.R1.COMPANY" value="ACME Construction" />

    OK, how do you do that? There is nothing in the grid control properties to allow adding that READONLY or javascript parameter. So you do it at runtime with code in the A5W page.

    Note that each line has an ID that looks like this: <Input id="V.R1.COMPANY", and that the value of Rx increments for each row and the word COMPANY is your control name. You need to modify that at runtime to say "<Input id="V.R1.COMPANY" READONLY.

    In the A5W page there is a line similar to:

    ?x_componentname.Output.Body.Grid_HTML

    Just above that put:

    Code:
    <%a5
    x_componentname.Output.Body.Grid_HTML=stritran(x_componentname.Output.Body.Grid_HTML,".COMPANY\"",".COMPANY\" READONLY")
    %>
    And then repeat that for each field you want to render readonly.

    Caution - the READONLY parameter is relatively new and requries a modern browser. Also, my example used COMPANY as the control name. For this you really should use obscure control names because the stritran() function will replace all occurances of whatever you specifiy.
    Steve Wood
    See my profile on IADN

    Comment


      #3
      Re: Limit Textbox Lookup to an item in the lookup Window

      Thank you Steve. That worked. I thought I would record what I did for anyone that might be having troubles implementing your solution. Recording length is 3:30.

      Comment


        #4
        Re: Limit Textbox Lookup to an item in the lookup Window

        Ken,
        Thanks for the videos....they will be very helpful am sure for me and others ...hopefully will save Steve time in the future as well in not having to explain how to do what this thread shows.

        And an even bigger thanks to Steve for taking the time in the first place!
        Mike
        __________________________________________
        It is only when we forget all our learning that we begin to know.
        It's not what you look at that matters, it's what you see.
        Henry David Thoreau
        __________________________________________



        Comment


          #5
          Re: Limit Textbox Lookup to an item in the lookup Window

          Guys,

          I have tried to implement this within my dialog component and as a result changed some of the code.

          Code:
          <tr>
          <td><p align=left><%A5 ?x_dlg_link_obj_In.Output.Body.Dialog_HTML=stritran(x_dlg_link_obj_In.Output.Body.Dialog_HTML,".FrObject\"",".FrObject\" READONLY") %></p></td>
          </tr>
          Unfortunately, the field is not getting disabled. I know this solution is for a Grid component, but should this also work using the same method within a dialog component?

          Thanks,

          Denis

          Comment


            #6
            Re: Limit Textbox Lookup to an item in the lookup Window

            Hi,

            I am having another go at making a field in a Dialog readonly. I have modified my code by replacing;

            <p align=left><%A5 ?x_dlg_bl_add_new.Output.Body.Dialog_HTML %></p>

            with

            <p align=left><%A5 x_dlg_bl_add_new.Output.Body.Dialog_HTML=stritran(x_dlg_bl_add_new.Output.Body.Dialog_HTML,".ELLIPSE_CODE\"",".ELLIPSE_CODE\" READONLY") %></p>

            It still does not work. It seems to stop the dialog showing up at all.

            I then tried adding in the extra line between the existing;

            <table>
            <tbody>
            <tr>
            <td>
            <p align=left><%A5 ?x_dlg_bl_add_new.Output.Body.Dialog_Echo %></p></td></tr>
            <tr>
            <td>
            <p align=left><%A5 ?x_dlg_bl_add_new.Output.Body.Xbasic_Code_Errors %></p></td></tr>
            <tr>
            <td>
            <p align=left><%A5 x_dlg_bl_add_new.Output.Body.Dialog_HTML=stritran(x_dlg_bl_add_new.Output.Body.Dialog_HTML,".ELLIPSE_CODE\"",".ELLIPSE_CODE\" READONLY") %></p></td></tr>

            <tr>
            <td>
            <p align=left><%A5 ?x_dlg_bl_add_new.Output.Body.Dialog_HTML %></p></td></tr>
            </tbody></table>

            Still no good.

            Is this solution not suitable for a Dialog?

            Denis
            Last edited by den1s; 10-06-2009, 09:28 AM.

            Comment

            Working...
            X