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

Simple list lookup problem (bug?)

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

    Simple list lookup problem (bug?)

    I have a problem that has cropped up since installing the last build. It may have existed in a couple of the previous builds too; I'm not sure. I'm pretty sure this problem did NOT exist in build 1466_1044.

    Anyway here goes. I have a table with a simple list lookup defined in the field rules. The "Display as drop-down list box" option is checked. The "Allow Exceptions" option is marked "Allow any value". The "Auto Popup" is marked "Popup on Entrance".

    When the user tabs into the field, the drop-down list pops up with a list of salesman. If he types "J" to select "John Doe", "John Doe" is automatically entered into the field. If he then presses the {Tab} key to move out of the field, and presses {F9} to save the record, the record will not save. He can press {F9} repeatedly, and it still will not save. If he clicks two or three times on the "Save Record" button on the toolbar, it will finally save the record.

    Here are the work-arounds:

    1. If after typing "J" to select John Doe, the user presses the {Enter} key, and then presses the {Tab} key to move out of the field, the record will save when pressing {F9}.

    2. If the field rule "Auto Popup" option is set to "Do Not Automatically Popup", then the user only needs to type "J" to select "John Doe", press {Tab} to move out of the field, and {F9} will work fine.

    Can anyone verify this annoying problem? I'm fairly certain this is a bug introduced in a recent patch, because I didn't have this problem until recently.

    Thanks for any input.

    Nathan
    Tags: None
    #2
    RE: Simple list lookup problem (bug?)

    I'm also having problems since this last build.

    In my sets when I add info into fields for an attached dbf to the set, if this is the first information added to this dbf it won't save the first time. I have to add data, hit F9 (the data goes away) and then when I add data to those fields I'm fine.

    The problem only arises when I'm adding data to a field to a dbf in a set for the first time. It's like it has to link the linking fields first and doesn't save the data and then once it's linked I can add data no problem.

    Comment

      #3
      RE: Simple list lookup problem (bug?)

      Nathan,

      Just to see if this is a bug, build a new DB with just a few fields and and the field rule you seem to have the problem with and see if you still get the same situation for saving the record. If there is no problem with the test DB then you will know it is not a bug but something has gone wrong with your build. It may mean a simple delete of the field rule and rebuild.

      Hope this helps.

      Keith Hubert
      London.
      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: Simple list lookup problem (bug?)

        Bradley,

        I assume that you are still testing a new application. Empty all tables, pack and Database Compact. Now try and enter data. You should not have the problem any more. On the other hand it could be that your link needs to be rebuilt.

        Keith Hubert
        London.

        PS, Next time could you please create a new message for a new problem even if seems the same.

        KH.
        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

          #5
          RE: Simple list lookup problem (bug?)

          If I am understanding you correctly, you have the same problem I have. Where I first noticed the problem was in a set I have called "invoices". The parent table is called "Invoice header", which has a couple of fields with simple list lookups like I described above. I have a one-to-many link to a table called "Line items", which contains the items ordered.

          After the user enters a new invoice, tabs to the first line item and enters it, and then tries to enter the next line item, he has a problem. He can't move to the next item, because the first item isn't saved. Apparently it can't link to the parent table, because the last record isn't saved, to which the item is supposed to be attached.

          It took me a while to isolate the source of the problem, but when I finally did, the workarounds that I listed in my first post took care of it. Still, I would really like to see the problem fixed in a future patch.

          Nathan

          Comment

            #6
            RE: Simple list lookup problem (bug?)

            Keith,

            I did as you suggested, and the problem remains.

            Nathan

            Comment

              #7
              RE: Simple list lookup problem (bug?)

              Nathen,

              It sounds like you have duplicated a design flaw from your old set to the new one.

              Do you have this as a problem with Alphasports?

              If not then I beleive you should look at the way you have created the set.

              Could you post the new small app here so we can look and see what is going on.

              Keith Hubert
              London.
              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

                #8
                RE: Simple list lookup problem (bug?)

                Keith,

                Yes, the problem does occur in AlphaSports, in the pay_method field of the Invoice Header table, after I change the list lookup in the field rule to "popup on entrance".

                I have also attached a simple database which illustrates the problem.

                Nathan

                Comment

                  #9
                  RE: Simple list lookup problem (bug?)

                  Nathan

                  I tested your example and it works correctly for both existing and new records. If I tab into the lookup field, start typing any letter until an entry fills in, and then tab out of the field, save (F9) works correctly and the record is saved. If I don't tab out of the field, the record saves. Perhaps someone else will have different results, but I don't see a problem. Are you using a different sequence?

                  Jerry

                  Comment

                    #10
                    RE: Simple list lookup problem (bug?)

                    Nathan

                    I also tested Alpha Sports, modified as you suggest and have not problem there either. What A5 build are you using?

                    Jerry

                    Comment

                      #11
                      RE: Simple list lookup problem (bug?)

                      Jerry,

                      I am using build 1491_1048, and it occurs in both the full version and runtime.

                      To duplicate the problem, open the "test" table, and press {Ctrl}+{Enter} to enter a new record. Press {tab} to move to Field2. Press "L" to select "Luke". The field automatically is filled in. If you press {Enter} and then {Tab} to move to Field3, you will not have a problem. However, if after pressing "L" you press {Tab} to move to Field3, without pressing {Enter} first, you will not be able to save the record by pressing {F9}. At least, that is my experience on 4 different computers, running Windows 2000 and XP.

                      Nathan

                      Comment

                        #12
                        RE: Simple list lookup problem (bug?)

                        Nathan

                        Interesting. If I follow you exact sequence on the default browse, I do see what you mean. It appears that the record may be saved, but you can't move focus off of the record until you hit enter or move focus off of the form. If I follow the same sequence on the default form, The status line does show the record is saved and I can move to another record with pgup and pgdn. Another interesting aspect is that Pgup does work on the browse after F9, however, the arrow keys don't. I will send an example off to Alpha if they haven't been following the thread. That doesn't seem correct.

                        Jerry

                        Comment

                          #13
                          RE: Simple list lookup problem (bug?)

                          Thank you, Jerry! I know it's a minor issue, but it creates more problems in more complex forms, so I hope Alpha can fix it.

                          Nathan

                          Comment

                          Previous template Next
                          Working...
                          X