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

Table lookups

  • Filter
  • Time
  • Show
Clear All
new posts

  • Table lookups

    I'm working on a jobcosting db/set for a printing company. An Operations table contains 6 fields > oper_id, oper_desc, mr_cost1, mr_cost2, op_cost1, & op_cost2 (these last 4 are numeric fields and are similar to discount levels in an inventory/sales application). I want to use this table for lookups from a related line-item table (op_costs.dbf) that is accessed from JobCost form (a set form). I want to pick one of the 4 prices when entering a line-item but I always get the price from the 4th column.
    On the Lookups sheet I point to the Operations.dbf table, have all 4 fields listed in the "linking field," and then the same 4 fields listed in the browse table on this sheet with them all filling in the "cost" field from the op_costs table. The Job Cost form does have a field called "Rate" (1 or 2 are the values) that could be used as to help narrow the choices down to 2 of the 4 fields, but I'm not even sure how to do that.
    Any help would be appreciated.

  • #2
    RE: Table lookups

    I don't think the table lookup field rule is powerful enough to do what you describe. You may do better to build a custom lookup form, with browse object for the source table. In the OnRowDbleClick event of that browse you could assign the four values to variables, and then you could use the ui_get_list() listbox to permit the user to pick the one he wants to use...

    -- tom


    • #3
      RE: Table lookups

      Thanks for your suggestion - I'll try it, but I after I wrote my original msg. here I made some changes in both the form and several of the related tables. As mentioned I have a field in a related table (and on the first page of the main data entry form for job costing) called "Rate" with a value of either 1 or 2, where 1 is full price while 2 represents a global discount to the entire job that is selectively given to certain customers. In addition, I added a field in another related table (where line items get entered/selected when costing a job) called "op_type" where users can select "MR," "WU" or "RU" (make-ready, washup or run). I want to build a conditional lookup that would look like this in plain english:
      if Rate=1 and op_type=MR or WU then show the user the mr_cost1 column of values from the operations table
      if Rate=1 and op_type=RU then show the user the op_cost1 column...
      if Rate=2 and op_type=MR or WU then show the user the mr_cost2 column of the value from...
      if Rate=2 and op_type=RU then show the user the op_cost2 column...

      I've pretty much a novice with Alpha5 so I don't have a clue about building conditional expressions so any help would be appreciated.


      • #4
        RE: Table lookups

        A correction, the Rate value does not mean a global discount - it only changes the operations rate field that prices are pulled from, but this shouldn't change the conditional statements I'm wanting help on.

        Thanks again.


        • #5
          RE: Table lookups

          I'm still trying to find a solution to this conditional lookup problem and I'm getting an error I can't solve. Here's the logic I'm trying to use to control what field(column) shows up in a lookup (all the tables referenced below belong to a defined set):
          if Rate=1 from the Dockets table and op_type=MR from the Ops_Cost table then show the user the MR_rate_1 column from the Operations table.
          Here what I've tried using for an expression when trying to configure an expression under Field Rules > Lookups > Conditional Lookups in the Ops_Costs table: dockets->rate="1".AND.Ops_Cost->Op_Type="MR"lookupn(Operations->Mr_rate_1)
          This results in the following error msg.: "Extra characters at end of expression." Any suggestions would again be appreciated.
          One other question: are the IF ... Then of the expression implied - I can't find those in the Logical Operators list


          • #6
            RE: Table lookups

            Bill, I think the Conditional Table Lookup field rule may not be powerful enough to do what you are attempting. Instead of 'conditioning' the identity of the lookup table on values in the same table for which the field rule is being defined, you are trying to use values from related records elsewhere in the set. i.e. in several different child tables. I'm not sure it's possible.

            Try a simpler set. Try to define a conditional table lookup field rule for a field in the parent table, using a 'condition' based on the value of a field in the child table of that set, to see if it's even possible. when I try to do it here, I do not see the related child tables 'available' in the expression builder.

            Unlike Alpha Four, this version of Alpha Five does not support set level field rules, which is what I think you would need to do this. Instead, all field rules are table level. The field rule engine for your parent table probably doesn't 'see' the fields in the related child tables...

            My suggestion would be to abandon the table level field rule lookups entirely, and roll your own. Input from the user stored in variables could be used to determine which related tables to present for further data entry or selection.

            -- tom