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

quick finds in lookup tables

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

  • quick finds in lookup tables

    I want to add the ability for users to "jump" to a item on a lookup table by just typing the first character of what they think an item is called. I've searched here and looked at Dan Mass's article on "Intelligent Lookups" & Dr. Wayne's article on "Self-Filling Lookup Fields" at the LearnAlpha site but they're not quite what my customer wants. Dan's req's adding another column to the embedded browse where the lookup is done & our space is too tight already (I'm also intimidated by the scripting) and Dr. Wayne's appears to keep the user working in the field in the embedded browse table but my customers want to be able to work from the lookup table (some are very long and there's not always been a consistent method for filling in the descriptions of each line item so they're convinced that having the lookup table popup into view is best).

    I've attached a sample set that uses a lookup table (specifically, a table of printer services and rates) that popups when you get to the "Oper id:" field in the default form of the Press_Costs table. Currently, you have to scroll thru the list of line items which is quite long in the working app that this sample is taken from. My customers would like to be able to just start typing the first several characters and have the selection bar "jump" down to the line item that is spelled that way.

    I demo'ed them 2 commercial products that has something like this type of "jumping" and they prefer the 2nd of the 2 choices as described below.
    - In the Palm desktop (V 4) if you're in the address book and type in a "b" the selection bar jumps down to the first listing starting with a "b." If you follow it with any other character nothing happens and the sel. bar stays on that first selection beginning with "b";
    - In the PIM "Time & Choas" the first key stroke has the same result as above but when you key in a 2nd character (eg, "i") it jumps again to the first listing starting with "bi...", etc. This is the preferred kind of lookup.

    Can this be done in A5V4.5 and, if so, how? W/O extensive scripting if possible??

  • #2
    RE: quick finds in lookup tables

    Bill, it sounds to me as though you'll have to abandon to table lookup field rule, and create a second form that contains the lookup table in browse mode. This second form gets called from an event on your primary form, so that it opens up at the desired time.

    Put a field on that form to get the input from the user, and modify Dan's script to do a series of finds as the user types characters in the input field.

    -- tom

    Comment


    • #3
      RE: quick finds in lookup tables

      One of the things you might try that is not exactly what you want, but closer, is only have the lookup popup on a mismatch. Have the lookup sorted by let's say name. When you get to the field, type in the first few characters of the name and then enter. The lookup should popup and start at those names. While you're in the lookup there is also a find option.
      If your customer will only be satisfied with what you described, read Peter's article again, and use some variation of it. He has done all the hard work.

      John

      Comment

      Working...
      X