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

possible solution for lookup problems in 4.03

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

    possible solution for lookup problems in 4.03

    hi:

    i'm trying a new ??? fix for the lookup crashing after 8 lookups.


    what i thought i might try is using a dummy table placing the already filtered records from the real table and then using the dummy table for lookup with no filters. has anyone tried this approach? (don't want to waste my time if it is already proven not to work)

    i tried running a filtered query on the real table prior to it being used as a lookup, however it displayed all records so it didn't work.

    any help much appreciated!!

    regards,

    ed

    #2
    RE: possible solution for lookup problems in 4.03

    Ed,

    I think it would work but your users might not like the delay you'll get if you have to populate the dummy lookup table each time.

    Depending on your application it might be possible to populate the dummy lookup table once, when the user logs on for example.

    In either case you will need to watch for changes to the source table from which the dummy receives its values. As records are added or changed there, corresponding adjustments in the dummy will be needed.

    I'm fortunate that in most of my apps it's ok for the user to see all the records in the lookup table. Even though there are lots of records in the lookup table, Ctrl-K finds the desired record very quickly, so the users are happy. In some cases you don't want the user to see all the records in the lookup table, and I presume that's your situation. If it's not, and you're just trying to reduce the number of records displayed in the lookup I'd say don't bother. Teach the users to use find by key and show them all.

    -- tom

    Comment


      #3
      RE: possible solution for lookup problems in 4.03

      Hello Ed,

      Are you saying that the lookup "always" crashes after 8 lookups? That is pretty strange.

      Although your approach would work, is sounds a little extreme. If you were going to go this route I'd suggest that you do a quick query in xbasic and present the user with the choices in a ui_get_list_array() dialog.

      When you define a filtered lookup in the field rules, Alpha Five creates a filtered index the first time it is used. There are issues with filtered indexes, but if the filter is based upon a field in the lookup table then your filtered lookup should work ok. If you are filtering based on some 'outside' value (such as a variable) then all bets are off and my guess is you'll have problems.

      A simple filtered index should work fine.

      All this being said, you should upgrade to version 4.5. The indexes in version 4.5 are much more stable than in earlier versions. Also, the cost of the upgrade will be applied to your purchase of the version 5 upgrade......... and let me tell you, if you're going to continue working with Alpha Five, you will upgrade to version 5. It's unbelievable (IMHO).

      Jim

      Comment


        #4
        RE: possible solution for lookup problems in 4.03

        hi tom:

        unfortunately the lookup has to be filtered on two criteria. i'm posting open orders that must be filtered to the order number as well as they must have a back order outstanding. the record clone appears to work quickly as there are typically 50 records max.

        thanks for your reply!!

        if i get it to work i'll post the code.

        thanks again tom!!

        regards,

        ed

        Comment


          #5
          RE: possible solution for lookup problems in 4.03

          hi jim:

          thanks for the reply!

          "Are you saying that the lookup "always" crashes after 8 lookups?"
          yep ... exactly 8

          "but if the filter is based upon a field in the lookup table then your filtered lookup should work ok."
          i couldn't agree more, however the filter is compound on two fields and i've had trouble with this before (as have a few others.


          i will order the v4.5 now. i had been reluctant to purchase it as i have the unlimited runtime license for 4.03. it is my understanding the ver 5 will be out in june. is this still correct?
          also i've written enough xbasic to fill the trunk of a '53 studebaker, will this run on ver 5 as well?

          thanks again,

          ed

          Comment


            #6
            RE: possible solution for lookup problems in 4.03

            Jim,

            This is a known bug in 4.03 thru 4.5, including the last released build for 4.5, build 266. Filtered lookups using a browse will normally crash after 8 to 15 successive records. This has been reported a number of times over the last year or so, including another thread this past week. About a year ago, Selwyn me sent a test build, build 267, which eliminated the problem. Apparently, there was a problem with releasing previous lookups from memory. For a variety of reasons, it was not released.

            Now for the good news. This has been fixed in A5V5. I just tested a table this week that crashed in 4.5 and it works perfectly in A5V5. Another great reason to wait for A5V5, along with about a zillion other neat new features. Considering the completeness of the current beta, the tentative release date of June looks reasonable.

            Jerry

            Comment


              #7
              RE: possible solution for lookup problems in 4.03

              Ed,

              One of the last holdups for release of A5V5 is verifing backward compatibility. A number of people have been testing the beta with existing applications to check this. As of the last beta build, the problems are very few, relatively minor, and related to the many new features. All existing xbasic seems to run just fine. The rate of development has been amazing, with fixes and enhancements arriving almost daily. Every app I have runs well in A5V5 with very little updating, and a couple have extensive xbasic.

              The number of new features in A5V5 is almost mind boggling, with new little (and big) tweeks coming out with each build. At the developers conference last month, Selwyn said the online documentation, which is not yet complete, already totals over 1000 pages. This gives you some idea about the number of features available.

              The really great part is that nearly everything is run from genies which are very easy to use and effective. Even people like myself who usually avoided some of the old genies are going to find the new ones so complete and easy, that everything will be easier.

              Don't worry about "wasting" money on 4.5. Buy it, take advantage of the greater index stability now. Why? Alpha has announced that the purchase price will be applied fully to the A5V5 upgrade. You have nothing to lose. By the way, I have no connection to Alpha. I am just a user too.

              Jerry

              Comment


                #8
                RE: possible solution for lookup problems in 4.03

                hi jerry:

                thanks for the input.

                regards,

                ed

                Comment

                Working...
                X