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

progressive lookups

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

    progressive lookups

    I am using the 'classical' Chapman 'Progressive Lookup'.
    Everything works just fine in Action Scripting or in Xbasic.
    That said, I have a small problem with the lookup..
    When you type in part or all of the name, the 'type in' area turns blue and the picked 'customer name' also is blue... blue meaning it's highlited... BUT
    When you click on 'OK' or press "Enter" the background form is filled with the correct data, and the dialog box remains on the screen until you either press "Enter" or click on 'OK' again....
    Not earth-shattering as problems go, but it's a PITB to have to keep repeating the step. Especially if you have 'a bunch' of records to modify...

    the search routine is a converted action script that I have modified....
    In the event it's needed, I will send it along.

    Does anyone have the same problem????

    thanx
    D

    #2
    RE: progressive lookups

    Richard,

    I too, use Jim's progressive lookup extensively, but with a few minor modifications.

    I have never experienced a case of the dialog not closing properly when a selection is made.

    Perhaps you could post a (non) working sample for us to timker with.

    Louis

    Comment


      #3
      RE: progressive lookups

      I have several other variations of this script and do not have a problem with them.
      This script is preceeded (in an action script) by an action to go to the first record in the table...
      This was put in, cuz I kept getting end of file errors.
      Have not tried it lately w/o the 'fetch_first'...

      thanx for any comments
      D

      'Date Created: 17-Sep-2004 03:29:14 PM
      'Last Updated: 05-Nov-2004 03:50:16 PM
      'Created By : Dick Coleman
      'Updated By : R. Coleman

      'Open a Form layout, displaying all records in the layout. Set sort order.
      'query.filter = ".t."
      'query.order = "Cus_name_last+Cus_name_spouse_1+Cus_name_spouse_2"
      ''frm.=:form.ViewQueried("cusform_tabbed",query.filter,query.order,"")
      'frm.cusform_simple=:form.ViewQueried("cusform_tabbed",query.filter,query.order,"hidden")

      'Create an XDialog dialog box to prompt for parameters.
      DIM SHARED vTypeIn as C
      DIM SHARED vSelect as C
      DIM SHARED varC_result as C
      ok_button_label = "&OK"
      cancel_button_label = "&Cancel"
      DIM vSelect_rl_def_orig as C
      vSelect_rl_def_orig = "kl=c_customers,{keylist_build(\"H=.025,1:25[Last Name],2:25[Husband],3:25[Wife]\",''+recno(),left(''+Cus_name_last,25),left(''+Cus_name_spouse_1,25),left(''+Cus_name_spouse_2,25))}{Cus_name_last "= [varC-"vTypeIn]}"
      DIM vSelect_rl_def as C
      vSelect_rl_def = replace_parameters(vSelect_rl_def_orig,local_variables())
      varC_result = ui_dlg_box("Select a Customer",""%dlg%
      {region}
      Enter Last Name:| [.40vTypeIn!vTypeIn_changed];
      Type prompt here:| [%@vSelect_rl_def%.60,15vSelect];
      {endregion};
      {line=1,0};
      {region}
      "*15=ok_button_label!OK" "15=cancel_button_label!CANCEL"
      {endregion};
      %dlg%,""%code%
      If a_dlg_button = "vTypeIn_changed" then
      vSelect_rl_def = replace_parameters(vSelect_rl_def_orig,local_variables())
      a_dlg_button = ""
      end if
      %code%)

      'Conditional code follows. Executes only if the condition expression is True.
      IF a5_eval_expression("=Var-"varC_result=\"OK\"") THEN
      'Go to a specified record number in Form 'Customer_Information' .
      DIM var_recno_target as N
      var_recno_target = val(vSelect)
      DIM object_name as C
      object_name = ":"+"cusform_tabbed"
      DIM varP_Object as p
      'Get a pointer to the specified object
      varP_Object = obj(object_name)
      'Check if the specified object exists
      if .not. is_object(varP_Object) then
      ui_msg_box("Error","The object '"+object_name+"' does not exist.",ui_stop_symbol)
      else
      varP_Object.recno_goto(var_recno_target)
      end if
      END IF

      END

      Comment


        #4
        RE: progressive lookups

        Ok this is not good....
        First, when I went back and removed the 'go to first record', it seemed to help and there was no 'stutter' as the lookup list box was removed from the screen...
        Secondly, I loaded the new patch this am and went to work..
        All of a sudden, the lookup began to behave like it had before I put the 'go to first record' in as a 'fix'...
        Then the list in the list box began to disappear and the record that was displayed was not always the one I had picked....
        Next I put back the 'go to first record' that fires each time the event is called... At first it seemed to help..
        Then it started to give randomly inaccurate results and the list box list was wiped out (on the screen) but the type-in name remained hilited in the list box type-in area.
        So I went back to the previous patch (reloaded it) and went back to work....

        Just as a refresher.. the button can be clicked or I can press CTL+J and the OnPush event is fired...
        The OnPush event consists of two (2) actions in an action script... go to first record and play a script...
        the script is a cut-down, modified version of Jim's progressive lookup and is in xbasic...

        It would probably take me in excess of six hours to "make" a version of the app that I could send along to anyone interested; and I don't really have that much time to spare........ Going back to work on it some more
        Will be back
        D

        Comment


          #5
          RE: progressive lookups

          DON'T GO LOOKING AT THE DIFFERENCES CAUSED BY PATCHES...
          I've gone back to 2015 and the problem persists....
          Still workin' on it...
          D

          Comment


            #6
            RE: progressive lookups

            Boy, can you make a long thread just talking to yourself...
            Solution Number 1:
            There was a blank record at the beginning of the table when sorted alpha by customer last name....
            Began seeing a hilited blank line at the top of the list box and that's when most of the problems occurred..
            Eliminated the blank record (contained only the record id #) and MOST of the problems disappeared.

            Solution Number 2:
            The dlg box still 'stutters' whenever you don't type in the entire name.. If you leave part of a name in the hilited 'type-in' area, then the box will disappear, and reappear (sometimes with the list missing in the list box), but pressing enter or clicking on 'OK' allows the script to continue and the correct record is placed in the underlying form....

            Altho it's not a complete fix; at least I can do repeated lookups w/o having to leave the form and come back or restart A5...

            It's probably something that I did in the script that is causing the 'problem' and I'll work on it as I get time.
            First I have to finish the updating of the customer records....

            Sorry if I took up too much time/space...
            D

            Comment

            Working...
            X