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

Color and Font equations

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

    Color and Font equations

    Can some tell me why this equation doesn't work?

    if(Calc->Dental_Cat="IV" .OR. Calc->Hiv="Overdue", "RED", ""

    When checking it with the evaluation button in the editor is evaluates correctly but printing the report it doesn't. This equation is connected to the persons name field.
    I also tried to use the color and font equations on the Dental_Cat field and the HIV field. Thought maybe they wouldn't work on calculated fields, so instead I put it on the name field.

    Thank you
    Joe

    #2
    RE: Color and Font equations

    Joseph,
    I think it should be something like:
    if(Calc->Dental_Cat="IV" .OR. Calc->Hiv="Overdue", "RED ON WHITE", "BLACK ON WHITE")
    John

    Comment


      #3
      RE: Color and Font equations

      Thanks, tried your suggestion but no luck, it dosn't change anything.

      Comment


        #4
        RE: Color and Font equations

        I may be wrong here, but I think when you print reports the calculations do not take place. You have to create a variable to holds the values. Use a conditional object instead?

        Comment


          #5
          RE: Color and Font equations

          It should work, but as others have suggested, you may need "Red on White". Note that background colors won't print in report color equations. e.g. "Red on Yellow", the yellow will not print. This is a bug.
          Peter
          AlphaBase Solutions, LLC

          [email protected]
          https://www.alphabasesolutions.com


          Comment


            #6
            RE: Color and Font equations

            Peter,

            I agree with the original post. I tested exactly what was described, as I understand it. Color equations for calculated fields did not evaluate and perform.

            I seem to remember that someone was able to workaround this by putting the same expression in the color equation that determined the calculated field, instead of referring to the calculated field itself.

            Stan
            There can be only one.

            Comment


              #7
              RE: Color and Font equations

              Stan,
              I think the problem is the order of various events. I suspect that the color equation is evaluating before the calculated value is found. If my memory is correct, the solution you suggest is one I have used. Put the calculated expression in the color equation and the order will always be correct. Another quirk I have seen on reports is the inability of the report to find the value of a global variable. But if you create a calculated field that has a value equal to the variable, the report will print it. Example:

              ' From a script run before the report

              dim global title_text as c
              title_text = "This is a title"

              If the report addresses the field as var->title_text, it may or may not work. But create a calc field on the report and call it, for example, "title" and define it as "var->title_text" and the report will show it.

              Jerry

              Comment


                #8
                RE: Color and Font equations

                Jerry,

                I agree with the timing issue. Actually I think Alpha calls this "threading". As a layout is processed, certain parts take place along the "thread" at different times. If the result you want is not available at the time it is needed for the expression you want to use, it doesn't get evaluated.

                Oh well, at least it doesn't crash.

                Stan
                There can be only one.

                Comment

                Working...
                X