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 lookup - by Jim Chapman

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

  • Progressive lookup - by Jim Chapman

    I have been using Jim's progressive lookup for a while in v6. I am currently trying to convert to v8 but the lookup returns an error "Select a record" indicating that vSelect = "" after either a double click or using the OK button.

    Any help/thoughts greatly appreciated.

    Fred
    Fred

  • #2
    Re: Progressive lookup - by Jim Chapman

    Fred, give us some sample data and your script. We need to see how you're implementing this in vers 8.

    Comment


    • #3
      Re: Progressive lookup - by Jim Chapman

      Fred,

      Have a look at this feature in AlphaSports, Customer Info form.
      Regards
      Keith Hubert
      Alpha Guild Member
      London.
      KHDB Management Systems
      Skype = keith.hubert


      For your day-to-day Needs, you Need an Alpha Database!

      Comment


      • #4
        Re: Progressive lookup - by Jim Chapman

        Hi Tom,

        Exact same code as I was using in v6. Since posting I believe I have the problem down to this line:

        vCurrentLine=word_number_get(vList,vSelect,crlf())

        It's around line 200 in the original code. vList (the llist of current records) looks good, and the vSelect value is in vList, but word_number_get returns a zero. Any chance v8 handles the crlf differently??

        Sorry I'm not giving a lot more data here but I'm trying to cut this app over before business tomorrow AM. Otherwise I'll have to cancel and then have time to rewrite the search before rescheduling. Whoopee!! :)

        Thanks,

        Fred
        Fred

        Comment


        • #5
          Re: Progressive lookup - by Jim Chapman

          Any chance v8 handles the crlf differently??
          I suppose it's possible but I'd be surprised. Recommend you study your data. Will be glad to help but will need the script and sample data. Maybe others are more intuitive than me and can help based on what you've described thus far, but I'm signing off til you post sufficient data for me to see your script (not Jim's) run in context.

          -- tom

          Comment


          • #6
            Re: Progressive lookup - by Jim Chapman

            Thanks Tom, I understand.
            Fred

            Comment


            • #7
              Re: Progressive lookup - by Jim Chapman

              Originally posted by Tom Cone Jr View Post
              but I'm signing off til you post sufficient data for me to see your script (not Jim's) run in context.
              I use Jim's script a lot and in v8. Jim's script works for me in v8.
              Al Buchholz
              Bookwood Systems, LTD
              Weekly QReportBuilder Webinars Thursday 1 pm CST

              Occam's Razor - KISS
              Normalize till it hurts - De-normalize till it works.
              Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
              When we triage a problem it is much easier to read sample systems than to read a mind.
              "Make it as simple as possible, but not simpler."
              Albert Einstein

              http://www.iadn.com/images/media/iadn_member.png

              Comment


              • #8
                Re: Progressive lookup - by Jim Chapman

                Thanks Al,

                I went back to Jim's original code and am still having the same problem. Guess that tells me the problem must be related to my data.

                Meanwhile looks like time is running out. Oh, well, that will give me time to look at other alternatives.

                Thanks again,
                Fred

                Comment


                • #9
                  Re: Progressive lookup - by Jim Chapman

                  debug(1) is your friend...
                  Al Buchholz
                  Bookwood Systems, LTD
                  Weekly QReportBuilder Webinars Thursday 1 pm CST

                  Occam's Razor - KISS
                  Normalize till it hurts - De-normalize till it works.
                  Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
                  When we triage a problem it is much easier to read sample systems than to read a mind.
                  "Make it as simple as possible, but not simpler."
                  Albert Einstein

                  http://www.iadn.com/images/media/iadn_member.png

                  Comment


                  • #10
                    Re: Progressive lookup - by Jim Chapman

                    Yup, I hear that Al. Unfortunatly nothing seems to be able to keep word_num_get from returning anthing but a zero! I run exactly the same code against the exact same data in v6 and it works like a charm.
                    Fred

                    Comment


                    • #11
                      Re: Progressive lookup - by Jim Chapman

                      I had a similar problem with Jim's code that just started with the latest version of V8 1939_3146. I reported it as a bug. Selwyn replied that it wasn't a bug and gave me some new code to replace the existing. The old and new is below. This fixed the problem. BTW, I also reported the month_number() function is not working with the month of March in the latest build as well. This one was confirmed and will be fixed in the next patch.

                      Code:
                      '_____________________________________________________________________
                      'Code created by Selwyn Rabins due to bug report submitted.
                      	if atc("vlist_",a_dlg_button) = 1 then
                      	
                      	if a_dlg_button = "vList_Change"
                      	dim pos as n
                      	pos = atc("{data=" + alltrim(vselect),vlist)
                      	vCurrentLine = word_from_pos(vlist,pos,crlf())
                      	
                      	vReturnString = GetCurrentValues("vList_Changed",vCurrentLine)
                      	a_dlg_button = ""
                      	else
                      	a_dlg_button = ""
                      	end if
                      	end if 
                      '_____________________________________________________________________
                      'Original code below and commented out
                      
                      'if a_dlg_button = "vList_Change"
                      '	a_dlg_button = ""
                      '	vCurrentLine = word_number_get(vList,vSelect,crlf())
                      '	vReturnString = GetCurrentValues("vList_Changed",vCurrentLine)
                      'end if 
                      'if left(a_dlg_button,6) = "vList_"
                      '	a_dlg_button = ""
                      'end if 
                      '______________________________________________________________________
                      I'm not fluent enough in xbasic to know why the one works and the other doesn't or why this code has worked in V6, V7, and V8 up until the latest update.
                      Jim Coltz
                      Alpha Custom Database Solutions, LLC
                      A5CustomSolutions.com
                      [email protected]

                      Comment


                      • #12
                        Re: Progressive lookup - by Jim Chapman

                        Thanks a million for the quick response, Jim. It worked just great! I know I could have rewritten it ala Alpha Sports, and may have to eventually, but for now I'll just procrastinate.

                        Besides I really like Jim's (Chapman) code. My users are really pleased with the speed as well as the touch/feel of the lookup! My hat's off to the both of you!

                        And thanks to all who chimed in here. Whether you solved the problem or not, it's just a lot less lonely knowing that someone is out there ready to try to help.

                        Thanks,
                        Fred

                        Comment


                        • #13
                          Re: Progressive lookup - by Jim Chapman

                          Glad I could help. I've certainly received lots of help from this board and like to give back when I can.
                          Jim Coltz
                          Alpha Custom Database Solutions, LLC
                          A5CustomSolutions.com
                          [email protected]

                          Comment


                          • #14
                            Re: Progressive lookup - by Jim Chapman

                            Has anyone come up with a progressive lookup version that looks up values from right to left, so to speak? This would be helpful for fields that pad the first digits.

                            For example: enter 3 and get all results ending in 3, enter 34 and get all results ending in 34, enter 347 and get all results ending in 347 (such as 00000347).

                            Comment


                            • #15
                              Re: Progressive lookup - by Jim Chapman

                              Originally posted by CDeCinko View Post
                              Has anyone come up with a progressive lookup version that looks up values from right to left, so to speak? This would be helpful for fields that pad the first digits.

                              For example: enter 3 and get all results ending in 3, enter 34 and get all results ending in 34, enter 347 and get all results ending in 347 (such as 00000347).
                              Oops - better to post a reply... rather than a blank reply...

                              Actually you can control what you want by refining an index to have the values that you want in it

                              something like stripping out the leading zeroes.

                              Since you have only numbers in the character field, convert to a value, convert back to a character field and left justify it

                              ltrim(str(val(<yourfield>)),<maxnbrofdigits>)

                              or something like that....
                              Last edited by Al Buchholz; 09-16-2008, 08:17 PM.
                              Al Buchholz
                              Bookwood Systems, LTD
                              Weekly QReportBuilder Webinars Thursday 1 pm CST

                              Occam's Razor - KISS
                              Normalize till it hurts - De-normalize till it works.
                              Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
                              When we triage a problem it is much easier to read sample systems than to read a mind.
                              "Make it as simple as possible, but not simpler."
                              Albert Einstein

                              http://www.iadn.com/images/media/iadn_member.png

                              Comment

                              Working...
                              X