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
Devcon 2020 Goes Virtual! LEARN MORE >

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

The logic of it all

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    The logic of it all

    Hi Phorum,

    I have a logic problem that I can't seem to derive a solution. The long and short of it is a combination of converting an APP that I wrote for the client from A4 to A5V4 8 years ago as well as the client changing his method of charging his customer for the work he has performed.

    Here is the problem: There are 10 distinct variables to be defined, was the work performed on a holiday, a Sunday, a Saturday, before 8:00AM, or after 5:00PM. It gets stickier, some clients he merely adds a predefined value in each case, others he uses a multiplier. In any event it is possible for more than either one of the above to be true, if that is the case, he wants the highest value used. For further complication he uses different values in the adds/mults for each of his customers. These values are stored in his customers profile table and populated in the jobenter form via a lookup table.

    To date I have considered and applied for/next loops, select/case statements and arrays. In general I set all of the multipliers to "1" and all of the addons to "0".

    The 5 addons are: holadd, sunadd, satadd, b4add, and aftr_add.

    The 5 multipliers are: holmult, sunmult, satmult, b4mult and aftr_mult.

    At this point in time I use a select/case to determine which addon and which multiplier is the largest value in the respective group, this means that I have 2 expression modifiers. I think I am answering my question as I am typing . Now I need to set the addon value to "0" when the multiplier is prevalent and the multiplier to 1 when the addon is prevalent.

    Thank you all for any insight,
    efs

    Tags: None
    #2
    RE: The logic of it all

    Hi Phorum,

    I thought this attached script would solve the problem; however, I get an error message that arguement (holadd) is incorrect data type. I wonder now, should I have put the refreshes immediately after establishing their value instead of putting them all at the end.

    Need advice,
    efs

    Comment

      #3
      RE: The logic of it all

      Ed,

      I find I have the best luck with these kinds of things if I break the code up into small pieces, each of which is understandable. The solution is tediously developed because the number of permutations are large. (Especially if some of the hours to be billed occur in premium intervals and some do not.)

      If it were me, I'd arrange my script so that

      1) the interval worked is analyzed and broken down, hour by hour into various categories:

      saturday hours
      sunday hours
      holiday hours
      holiday + saturday hours
      holiday + sunday hours
      before 8 hours
      before 8 + holiday hours
      before 8 + holiday + saturday hours
      before 8 + holiday + sunday hours
      after 5 hours
      after 5 + holiday hours
      after 5 + holiday + saturday hours
      after 5 + holiday + sunday hours
      other hours (this category would catch hours that were between 8 & 5 and not on a holiday, saturday, or sunday)

      2) having assigned the number of hours that fall in each category, I'd then compute the cumulative hourly charge in each category using lookups to retrieve customer specific terms. I do it category by category until I'd finished billing for all the hours. Then I'd sum all the subtotals.

      this really is nothing more than doing it on paper, one step at a time, and then translating the steps into computer scripts.

      Good luck.

      -- tom

      Comment

        #4
        RE: The logic of it all

        Hi Tom,

        Thank you for responding, you did a great deal of thinking and typing. While having dinner just a bit ago, I thought about breaking it into 5 separate scripts. The reason that I elected to use select/case is because only one of the premiums get charged to a job, and the case statements are in the order of highest cost at the top decreasing as the flow goes thru the select statement. The script is supposed to perform several functions. The first being setting the appropriate operator value to the highest of holidays, etc. While at the end it insures that all other multpliers are set (refreshed) to 1 and all other addons to 0.

        I think it's a monster,
        Ed

        Comment

          #5
          RE: The logic of it all

          Hi Tom,

          I remarked out all lines in the script that refresh the fields in question and it seems to work perfectly, will that present a problem later on?

          Thank you for any insight,
          Ed

          Comment

            #6
            RE: The logic of it all

            Ed,

            the answer to that question turns on what else is happening on the form. I shouldn't think it will do any damage, since the lines you're commenting out simply update the display...

            -- tom

            Comment

              #7
              RE: The logic of it all

              Hi Tom,

              That is actually good news, I didn't know that the refresh only affected the display. When I think about it the word "refresh" is self explanatory.
              Thanks again for the umpteenth time,
              Ed

              Comment

                #8
                RE: The logic of it all

                Hi Tom,

                I deleted the refresh lines from the above script and had it on the ondepart event of the data entry form (parentform) named "jobenter" and it worked great. Suddenly the event doesn't fire when I save the form. Is there a better place to put the script?

                Thank you for any incite,
                Ed

                Comment

                  #9
                  RE: The logic of it all

                  OOPS, I meant the cansave event.

                  Age is setting in,
                  Ed

                  Comment

                  Previous template Next
                  Working...
                  X