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



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

Problem with Look-ups

  • Filter
  • Time
  • Show
Clear All
new posts

    Problem with Look-ups

    In my main Table "Logfile" I have two fields "Operator_Name" (52 Characters) and "Op_Unique" (8 Characters). In table "Operator" I have the same two fields plus "Country" (12 characters). The reason for the Op_Unique is that Logfile-> Operator values can be the same, but have different "Country" values.
    Currently I use the "Operator" table as a look-up for values for Logfile->Operator_name and Logfile->op_unique. This works just fine, but means I have redundant data in the Logfile->Operator_name field. When I update operator->Operator_name, I also have to update the Logfile->Operator_name field
    How do I go about creating a look-up for values in Logfile->Operator_name but only using the Logfile->op_unique field as the look-up value.(so that I no longer need the Logfile->Operator_name field)? ie when I update Operator->Operator_name the new value will be displayed in Logfile->Operator_name field.
    Support your local Search and Rescue Unit, Get Lost!

    RE: Problem with Look-ups


    When you retrieve the operator_name value from the lookup table and store it in your logfile table record that preserves the value of operator_name as it existed at the time the transaction is saved. This is often desirable, indeed essential.

    If you now want the current value of operator_name to be shown whenever you view related records in the logfile table you will have to change your design. Instead of using lookups to retrieve operator_name values and storing them in the logfile, you could create a set linking the lookup table to your logfile table through some common key field. Then, instead of storing the operator_name in the logfile it would be available through the set. If the value of the operator_name changes, the current value will always be available. This is often desirable, indeed essential. HOWEVER, this approach prevents you from knowing what the value of the operator_name was at the time of the transaction, since it only shows the current value.

    To recap. One would link related tables to have current informaiton always available. One would LOOKUP field values when one wants to record what those values were at the time the pending transaction is saved.

    -- tom


      RE: Problem with Look-ups

      yep got all that. Presumably I cannot have both! if I use the Logfile->Operator_name on the set Form I can use the lookups to change the record OR I can use the Operator->Operator_name but then I am unable to use lookups.
      Support your local Search and Rescue Unit, Get Lost!


        RE: Problem with Look-ups

        since the scenarios I described are mutually inconsistent why would you want both?

        -- tom


          RE: Problem with Look-ups

          the Logfile->Operator_Name can change quite regularly, and its quicker to use the lookup facility to change it. But it would still be nice to be able to change all occurrences at once. Maybe I need to write a script that I can run against the Operator->Operator_Name that will update Logfile->Operator_Name on the saving of the updated record in Operator->Operator_name?
          Support your local Search and Rescue Unit, Get Lost!


            RE: Problem with Look-ups

            Sounds as though you want the 'current' value of operator_name, regardless of what it might have been when the first transaction was recorded. This is similar to wanting the current fax phone number, instead of the original fax phone number when a member joined up, in my application. Instead of looking up this kind of data, I store it in a child table that I link to theprimary table through a transaction idnumber. Then, if the fax number changes I just change it in one place... i.e. the child table. No update through the primary table is required. Maybe something like this would be of use to you.

            -- tom