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

Using Calc. Field in a Lookup Table

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

    Using Calc. Field in a Lookup Table

    Is it permissible to use a table calculated field in a lookup table?

    I have tried to do this and get an odd effect where the lookup displays only every other record. Otherwise, it appears to behave like an ordinary field.

    All observations welcomed.

    Dennis

    #2
    RE: Using Calc. Field in a Lookup Table

    Dennis, I think this is ok.

    To test it, I defined a new field in my table. Then used field rules to classify it as a calc field (instead of user entered). The calc expression is simple, I concatenated two other character fields in the same table into one long character string. I then built an index on the calc field, in ascending order.

    In a second table, I added another character field to the table's structure. For this field I defined a table lookup field rule pointing to the calc field in the first table.

    Works like a charm.

    If your's is continuing to skip records, I'd check the calc field expression carefully. Perhaps theres's something there that can explain it. I'd also check the way I'd defined the lookup to make certain I did not inadvertantly filter out some of the records in the lookup table.

    Hope this helps get you back on track.

    -- tom

    Comment


      #3
      RE: Using Calc. Field in a Lookup Table

      Denns - another thought...

      You should check the calc field using the default browse for your table. It's possible some are blank if your field rule defining the calculation was not in effect when these records were added to your table. When you add a field rule like this Alpha Five does not back up and re-evaluate all the previous records for you...

      -- tom

      Comment


        #4
        RE: Using Calc. Field in a Lookup Table

        Hi to both of you,

        Are we talking about a calculated field (which is not stored) or a regular field whose contents are generated by a calculated field rule as I think Tom has interpreted you to mean.

        As Tom verified, the latter case is fine for your purposes but I have doubts about the former.

        Bill
        Bill Hanigsberg

        Comment


          #5
          RE: Using Calc. Field in a Lookup Table

          Bill is right. The terminology here can become confusing quickly. I was not talking about the 'global calculated fields' which can be defined from the 'table' menu while editing the structure of a table. I have never tried to used one them as the source for a lookup. Instead, I was talking about a regular character field in the table itself, for which a field rule has been defined to limit it to a specific value determined by the calculated expression.

          -- tom

          Comment


            #6
            RE: Using Calc. Field in a Lookup Table

            Tom,
            Thanks again for coming to my aid.
            I found the problem with record skipping in the lookup table. It was because the data used by the calculated field had already been entered. After re-entering and carrying out a re-evaluation of the field rules it behaved correctly.
            The use of the calculated field in a lookup table - once all the links had been properly established - works just fine. There is a multiplicity of linked tables, reports and letters associated with this, all of which work correctly.

            Thanks for your help.

            Comment


              #7
              RE: Using Calc. Field in a Lookup Table

              Bill,
              It is a table calculated field which, as you know, is stored.

              You will see from my reply to Tom Cone that I have cured the problem with record skipping in the lookup table. The data had to be re-entered. Now everything works just fine.

              Thanks for your input.

              Dennis

              Comment


                #8
                RE: Using Calc. Field in a Lookup Table

                Tom,
                My reply to Bill answers this question I think.

                Regards,

                Dennis

                Comment

                Working...
                X