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
Devcon 2020 Goes Virtual! LEARN MORE >

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

Using Autosuggest Lookup with Search box via Table View

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Using Autosuggest Lookup with Search box via Table View

    Hello,

    I've configured a grid using a view to combine fields into the same grid from two tables.

    The problem I've got is Autosuggest lookup(in the search field) wont work on any of the fields from either table 1 or table 2.

    This must be a limitation of grid components? Is there another way of combining to tables into one grid without having to use the grid linker?

    Many Thanks

    Tim
    Tags: None
    #2
    Re: Using Autosuggest Lookup with Search box via Table View

    I'm using Oracle Express and autosuggest works on fields in a view. See pic. I have used this feature for one of the search fields from the view.

    I've tested this with a field for which I created an index for the autosuggest field on the underlying table (of the view) and it also works on a field of the view for which I did not create an index in the underlyng table...

    Mind you the autosuggest field is case sensitive so make sure you start entering with capital if your list starts with it.


    !! Later after more testing:

    I've noticed that it might certainly matter to define an index on the autosuggest field !
    The first test on the field I did not create an index on, was actually the first entry in the view...But entries further on did NOT show up.
    So: try creating an index on all the fields you are using for your autosuggest.
    Let me know if you had success with that.
    Last edited by rleunis; 09-09-2009, 03:52 PM. Reason: forgot the pic and did some more testing

    Comment

      #3
      Re: Using Autosuggest Lookup with Search box via Table View

      Is there another way of combining to tables into one grid without having to use the grid linker?
      You can create a view as part of the grid definition (DBF DB) see PIC. (Under Grid > Query (DBF))

      Using A SQL DB you can create a view there and base your grid on that.
      Last edited by rleunis; 09-09-2009, 03:43 PM. Reason: typos

      Comment

        #4
        Re: Using Autosuggest Lookup with Search box via Table View

        Or you could follow Selwyn's recent suggestion. Because hard disk's are cheap - just add fields to your parent table and forget all about relational databases.

        Comment

          #5
          Re: Using Autosuggest Lookup with Search box via Table View

          Originally posted by Lance Gurd View Post
          Or you could follow Selwyn's recent suggestion. Because hard disk's are cheap - just add fields to your parent table and forget all about relational databases.
          ....!!!! Which recent suggestion of Selwyn? Where did he suggest this?

          Are you or he serious?

          Why using a relational DB then anyway? Just use one big XML file as your database...

          Comment

            #6
            Re: Using Autosuggest Lookup with Search box via Table View

            Hey Ron,

            Firstly I started with a clean slate and recreated again what I previously attempted and wolah! it worked straight off.

            So I compared my previous component and the new one and there were no differences, hmm just one of those things :(

            The auto suggest in the search field works ok and isn't case sensitive.

            Once again thankyou for your kind help.

            Comment

              #7
              Re: Using Autosuggest Lookup with Search box via Table View

              Originally posted by rleunis View Post
              ....!!!! Which recent suggestion of Selwyn? Where did he suggest this?

              Are you or he serious?

              Why using a relational DB then anyway? Just use one big XML file as your database...
              I am afraid I think Selwyn was serious, this is the e-mail interchange between us

              First a reply from Selwyn to what I considered a bug
              >Lance
              >
              >I have been contemplating your bug report about the edit-combo for the
              >situation where you display a different value than you return.
              >
              >You reported that there was a bug because when you typed into the
              >control, the value that you typed was filtering the display based by
              >search in the return value fields and not the display value fields.
              >
              >After thinking about this for a long time, I have concluded that we do
              >NOT consider this to be a bug.
              >
              >This is what you should do:
              >
              >Say that wanted to define the edit-combo to display: Lastname, and
              >return: customer_id
              >
              >You should define the edit-combo for the 'Lastname' field.
              >You should have a customer_id field on your grid, but you can set it's
              >control type to "hidden"
              >
              >You should change the edit combo to display: "Lastname", return:
              >"Lastname" and fill-in: customer_id (the hidden field)
              >
              >then, when you interact with the edit-combo, typing will filter the
              >list as you expect.
              >
              >when you make a selection, it will fill in the value into lastname
              >(which you don't care about), but it will also fill in the hidden
              >customer_id field with the customer_id value (which is what you want)
              To which I replied and got RED Replies from Selwyn
              >Selwyn,
              >
              >Doesn't that negate the, sometimes, whole purpose of a look-up?

              no, i don't think that it does.




              >How would you do this in Alphasports invoice items table for instance
              >where the product_id is stored but the product description is shown,
              >you would either have to add another field to the table for the product
              >description or add a calculated field to the grid, both adding overhead
              >to the table!

              you would add another field to the table. when 1 terrabyte disks cost $60, i would not worry too much about adding an additional field to the table.
              I am now flattening and enlarging my tables to get edit-combos to work in look-ups how they work on the desktop, I love the way V10 works but find this a big stumbling block.

              Flat large tables may take up more disk space and slow things down marginally but coding them is a lot easier :p

              Comment

                #8
                Re: Using Autosuggest Lookup with Search box via Table View

                I agree (if I understand your issue correctly..) that the edit combo feature should facitate a field (computed) to enter the data (based on your selected attributes) which then automatically fills the field with the id value the return field needs...

                Adding a field in your table which makes this feature works jeopardises relational DB relational / normalisation standards.

                Interesting discussion...

                Most IDE's do not offer this Alpha combo feature.
                Usually it's just a dropdown only.

                So maybe experience is needed to make this more mature...

                Comment

                Previous template Next
                Working...
                X