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

New Calculated and Variable Fields in Set Design Mode

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

  • Peter.Greulich
    replied
    Re: New Calculated and Variable Fields in Set Design Mode

    There is a new layout for the Set Design View that includes two tabs for calculated and variable fields
    FYI: These have existed in ALL versions of A5.

    Leave a comment:


  • New Calculated and Variable Fields in Set Design Mode

    With the latest update to alpha 5 v 10.5. There is a new layout for the Set Design View that includes two tabs for calculated and variable fields. I was curious to know how these fields work. Can I use the new variable fields in the set in the following way?...

    I have a set with a Parent, Child, Grand Child, and a great grand child. tables linked by are single ID field in the parent table.

    tblProjects
    |
    |===>tblWorkOrder(1:M0
    |
    |
    |=====>tblworksheets
    |
    |=====tblworksheet_items
    |=====>tblworsheet_trucks
    |=====>tblworksheet_employees

    When I an record to the item, trruck, or employee table I need to determine which bill to use for the item, employee, or truck record. This isn't a simple lookup because the rate is determined by the customer the work is being done for as well as several other factors. For example the rates table for the items has the following fields....

    Rec_no
    Cust_Id
    Item_Code
    Itm_desc
    Itm_Units
    Bill_Rate1
    Bill_Rate2
    Bill_Rate3
    Pay_Rate1
    Pay_Rate2
    Sub_Rate1
    Sub_Rate2
    Sub_Rate3
    Sub_Rate4

    Which bill rate and pay rate to use is determine by a value in the tblworksheet table(tblworksheet->bill_Rate_id and tblworksheet->pay_rate_id. Also stored in the WorkOrder table is a field that indicated whether to the rates should be multiplied by 1.5 for overtime. So I created a UDF field to look up the value of bill and pay rates fields in the tblworksheet_items table...

    item_rates(tblproject->Cust_ID,tblworkorder->OT,tblworksheet->Bill_Rate_ID,tblworksheet_Items->item_code)

    Since most of these values come from different tables I was using lookup() functions to determine the values of the parameters for the my UDF (Item_Rates()). I soon realized that this was too much calculating and was way too slow for efficient data entry.

    So I then created fields in the tblworksheet_items table for each parameter in my item_rates udf that was currently retrieved by a lookup() function. Each of these fields had a field rule with a "Simple Initial Value" which contained a calculation for retrieving the value needed in my udf. So now my tblworksheet_itme->bill rate field, I had a calculated value using my UDF that looked like this

    Items_Rates(Cust_id,Overtime, bill_rate_id,Item_Code)

    I also had written code for the tblproject->cust_id, tblworkorder->overtime, and tblworksheet->bill_rate_id,field rules that were triggered by the events->CanWrite. The code would audit the changed value and pass that value to the great geand child table linked to the record being changed and then recalculate the bill rate for those records. (ie if the customer on the project is changed after workorders, worksheets, and worsheet_items were added to the that project, then the rates for that new customer would be applied to the current worksheet_items.

    Now I am wondering that instead of having to do lookup in the worksheet_items table for these values in different tables in the my set, can I simple have a function in a calculated field that uses values stored in the "set variable tab" so my new Itesm_rate() UDF in the tblworksheet_items table would be

    item_rates(var->Cust_ID,var->Overtime,var->Bill_rate_id,var->item_code)

    If this would not work, what would you all suggest the best way to go about calculating these rates would be???
Working...
X