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

'Help like' record search

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

  • martinwcole
    replied
    RE: 'Help like' record search

    well, figured out how to simplify and greatly speed up the search

    use this as the query instead

    query.filter="alltrim(lower(var->tempstr)) $ lower(lastname))"

    Leave a comment:


  • martinwcole
    replied
    RE: 'Help like' record search

    here is a sample app with the script using 12,500 customers

    Leave a comment:


  • martinwcole
    replied
    RE: 'Help like' record search

    got to thinking about your request, and thought, "The script I used will work perfectly if the user knows the correct beginning characters for the value they are searching for - but what if they don't know the correct beginning value?!!"

    have successfully experimented with the following change to the below line - the first part looks for the value at the beginning of the field and the second part (following the .or.,) searches for the value anywhere in the field.

    While in theory you would only need the second half - when I use the second half only, it will only find values within that field that are NOT at the beginning - but this query is working like a charm in my little dialog form. I don't know why I have to have both parts of the query - but who cares, if it works! If you have only a few thousand records in your lookup I think it will work okay - but if it were used on a massive bunch of records it might be slow as it would be an extensive query.

    In a scnenario like this my client doesn't care if there is a pause, he only cares whether ANY operator with ANY level of compentence can get it to work!

    query.filter="left(lastname,"+ltrim(str(len(tempstr)))+")='"+tempstr+"' .or. *any(lastname,alltrim(var->tempstr))"

    Leave a comment:


  • Jimmie1234
    replied
    RE: 'Help like' record search

    Will try it!!

    Thanks for the input.

    Jim

    Leave a comment:


  • Jimmie1234
    replied
    RE: 'Help like' record search

    Thx Cal,

    I've looked at that approach...trouble is it makes the user start to have to think.....:)))

    The user for this app is most probably going to be a warehouse helper (minimum wage)who just needs to type a few letters, look at a list, and hit enter and thereby find the item according to the bin or rack its in. Mouse use or tool bar use is too complicated. Thanks for your suggestion.

    Jim

    Leave a comment:


  • CALocklin
    replied
    RE: 'Help like' record search

    Wouldn't a "Find Text" work here? If you use Xbasic, you could even script it to be a little more user friendly. unfortunately, 'more user friendly' often means 'less versatile' so you'll have to decide whether to set up something specific or just show them how to use the "Find/Find Text" menu item.

    Leave a comment:


  • martinwcole
    replied
    RE: 'Help like' record search

    Here is a modified version of one of Dr. Wayne's scripts. In my main form, if the user pushes F10 I pop up a 2nd form as a dialog with an embedded browse based on the customers table showing only the first name and last name in the embedded browse.

    at the main form:
    onkey event:
    '*********** CUSTOMER SEARCH
    if a_user.key.value="{F10}" .and. a_user.key.event="down"
    a_user.key.handled=.t.
    ans=""
    f=form.view("customerquick","dialog")
    f.close()
    if ans "yes"
    end
    end if
    this.index_set("custid")
    this.find(custnmbr)
    'custnmbr is a global variable
    'the parent table "contracts" has an index called "custid"
    end if


    This code is placed at the "Onkey" event
    for that 2nd form.

    as they type the characters of the last name, it will isolate and display appropriately.

    I give then the F5 key on the 2nd form as a way of "starting over" in their search.

    as the customers are isolated, if they move up or down with the arrow key, and then press "Enter," I close the form capturing the global variable "custnmbr"

    'code for Customerquick

    dim shared tempstr as c
    dim shared posn as n
    dim shared check as c
    dim tbl as p
    dim idx as p
    if a_user.key.value="{F5}"
    a_user.key.handled=.t.
    posn=0; tempstr=""
    browse1.activate()
    browse1.fetch_first()
    end
    end if
    if a_user.key.value = "{ESC}" .and. a_user.key.event="Down"
    ans="no"
    gpc="Y"
    this.cancel()
    this.close()
    end
    end if
    if this.active()="browse1"
    if a_user.key.value="{ENTER}" .and. a_user.key.event="down"
    a_user.key.handled=.T.
    tbl=table.current()
    custn=tbl.custid
    gpc=tbl.mapsco
    ans="yes"
    this.close()
    end
    end if

    tbl=table.current(1)
    tbl.index_primary_put("name")
    if a_user.key.event="down"
    if left(a_user.key.value,1)="{" then
    ' it's a special key or backspace or function key
    select
    case a_user.key.value="{BACKSPACE}"
    if posn>0 then
    posn=posn-1
    tempstr=iif(posn=0,"",left(tempstr,posn))
    end if
    case a_user.key.value="{LEFT}"
    posn=iif(posn>1,posn-1,0)
    case a_user.key.value="{RIGHT}"
    posn=iif(posn1,left(tempstr,posn),"")+substr(tempstr,posn+2,len(tempstr)-posn)
    case a_user.key.value="{END}"
    posn=len(tempstr)
    case else
    ' do nothing
    end select
    ' pass all special characters to form
    a_user.key.handled=.f.
    else
    if posn=len(tempstr) then
    posn=posn+1
    tempstr=tempstr+a_user.key.value
    else
    tempstr=left(tempstr,posn)+a_user.key.value+substr(tempstr,posn+1,len(tempstr)-posn)
    posn=posn+1
    end if
    a_user.key.handled=.f.
    ' check to see if a unique name can be matched
    query.filter="left(lastname,"+ltrim(str(len(tempstr)))+")='"+tempstr+"'"
    query.order="lastname"
    query.options="I"
    idx=tbl.query_create()
    if idx.records_get()=1
    ans="yes"
    custn=tbl.custid
    gpc=tbl.mapsco
    this.close()
    end
    end if
    browse1.refresh()
    idx.drop()
    end if
    end if ' a_user.key.event="down"
    end if

    hope this helps

    Leave a comment:


  • Jimmie1234
    started a topic 'Help like' record search

    'Help like' record search

    I've been playing around with this inventory app for sometime now, learning as I go. I have tried a number of different ways to make it easier for a user to find an item in the database for making changes or using in a transaction process. I like the way that the Windows HELP function works in the index mode (as you type the letters in a search the list window automatically zeroes in on the item that matches the typing).

    This would be ideal for my app in which a user may only know a snippet of information about an item, not necessarily what user defined field to look in and how the complete field entry was originally entered. e.g.: The user might know that the item is a 14' roll of vinyl in a certain style, and is trying to identify which project it may have been ordered for or on which purchase order.

    The number of items in the inventory is large and the expertise level of the user is rather low in terms of using a PC. Any suggestions as to how this can be(or where it has been) implemented?

    Jim
Working...
X