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

Invisible Lookups from v7 to v9

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

    Invisible Lookups from v7 to v9

    We upgraded from v7 to v9. We have an existing database completely developed using alpha5 v7. Several items in the data entry form use a table lookup which links to a smaller database as defined in the field rules, that is supposed to force closest match and popup on entrance. This worked fine in v7 (and still does), but in v9 the popup drop-down list is populated with invisible entries and doesn't force match.
    The link still exists because if I type enough letters to disambiguate the entry and then tab over to the next field, it completes (bo becomes Bob if there are no other bo's in the table). Also, if I grab the slider with my mouse, the tooltips will show the table entries as I scroll. The purpose of the table lookup with force match and popup was to ensure data integrity, to maintain that part numbers get entered as "pn-2" rather than "pn2" or "pn 2" etc.

    Why can I no longer see my drop-down? And why does it no longer force match?

    What broke in v9 and how do I fix it?

    We're running Alpha5 version 9 platinum, build 1600/build 3196.

    #2
    Re: Invisible Lookups from v7 to v9

    Your build looks pretty out of date to me. Is there some reason you've elected not to install later builds?

    Comment


      #3
      Re: Invisible Lookups from v7 to v9

      Originally posted by Tom Cone Jr View Post
      Your build looks pretty out of date to me. Is there some reason you've elected not to install later builds?
      No reason other than I was unaware there had been updates. I just updated to 1772/3208, but it didn't fix the problem.

      Comment


        #4
        Re: Invisible Lookups from v7 to v9

        Have you tried re-building the lookup with the new version?

        Make a backup copy of you db first though just in case everything gets messed up.

        Comment


          #5
          Re: Invisible Lookups from v7 to v9

          Tried updating the indexes, no luck.

          I *could* change it back to a simple lookup, but then I'd lose the alphabetized ordering.

          Perhaps I'm using the wrong control. I've got it as a type-in field.

          What kills me is this works just fine in v7.

          Comment


            #6
            Re: Invisible Lookups from v7 to v9

            Just to get a visual on what's going on here:



            All programming for this database was done in the wysiwyg editor.

            Comment


              #7
              Re: Invisible Lookups from v7 to v9

              My experience of this happening is that Alpha automatically builds an index for the lookup and uses the first available field in the lookup table. If the first field of the lookup table contains empty fields or field containing the same values, then the index throws up anomolies.

              So I tend to move the first field down in the table structure and move up to the top of of the structure a field that I can count on to be filled and unique.

              This is only my observation and not based on any technical expertise

              Michael

              Comment


                #8
                Re: Invisible Lookups from v7 to v9

                The lookup tables consist of a single field, so that isn't it.

                Comment


                  #9
                  Re: Invisible Lookups from v7 to v9

                  What does the lookup data actually consist of? You say it is another smaller database, is it an Alpha 5 db?

                  Is it just one field from a table it is using? Have you tried alltrim(fieldname) to trim invisible empty spaces?

                  The three dots in the bottom right corner of the V9 lookup indicate it is re-sizeable, have you tried dragging the bottom right corner of the V9 lookup drop down to re-size it? It maybe a sizing problem? If not have you got an example db that you can post to this thread so we can take a look?

                  If you are going to post this make a list of actions we need to take to reproduce the problem ourselves.
                  Last edited by Alastair; 10-27-2008, 12:14 PM.

                  Comment


                    #10
                    Re: Invisible Lookups from v7 to v9

                    Originally posted by Alastair View Post
                    What does the lookup data actually consist of? You say it is another smaller database, is it an Alpha 5 db?
                    Yes, it is an A5 database.

                    Is it just one field from a table it is using? Have you tried alltrim(fieldname) to trim invisible empty spaces?
                    Where would I put the alltrim? In the form control properties?

                    The three dots in the bottom right corner of the V9 lookup indicate it is re-sizeable, have you tried dragging the bottom right corner of the V9 lookup drop down to re-size it? It maybe a sizing problem?
                    Tried, resizing, no luck.

                    If not have you got an example db that you can post to this thread so we can take a look?
                    Attached .zip

                    If you are going to post this make a list of actions we need to take to reproduce the problem ourselves.
                    • Open the form: Lookup Form
                    • Create a new record
                    • Click the dropdown box or try to type a new Lookup value
                      Items in Lookup Table
                    • Data
                    • Datum
                    • Fill
                    • Field
                    • Test
                    • Value

                  Comment


                    #11
                    Re: Invisible Lookups from v7 to v9

                    Solved. Thanks JerryBrightbill.

                    Comment


                      #12
                      Re: Invisible Lookups from v7 to v9

                      Elizabeth,
                      Please present your solution for others who may find this later and need the same.....
                      Mike
                      __________________________________________
                      It is only when we forget all our learning that we begin to know.
                      It's not what you look at that matters, it's what you see.
                      Henry David Thoreau
                      __________________________________________



                      Comment


                        #13
                        Re: Invisible Lookups from v7 to v9

                        Elizabeth,


                        I couldn't open any of the tables or forms in the database you supplied!

                        Glad you solved your problem!

                        What was causing it?

                        Comment


                          #14
                          Re: Invisible Lookups from v7 to v9

                          Alastair, her zip file contains a small database which illustrated her problem perfectly. Way to go Elizabeth!

                          Elizabeth correct me if I get this wrong, but the fix was based on realizing that the table lookup field rule was no longer properly defined. The grid (columns "Source", "Fill", "Display") was empty. Mapping the lookup "source" field to the primary "fill" field, and choosing "Yes" for "Display" solved the problem.

                          Comment


                            #15
                            Re: Invisible Lookups from v7 to v9

                            Originally posted by Tom Cone Jr View Post
                            The grid (columns "Source", "Fill", "Display") was empty. Mapping the lookup "source" field to the primary "fill" field, and choosing "Yes" for "Display" solved the problem.
                            Precisely. For some reason in version 7, it works fine without that, hence the confusion.

                            Comment

                            • Working...
                              X