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

Color in a form

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

    Color in a form

    I have a small table with a field "Color" which allows the user to set the display color of items belonging to a category. I am using a slightly modified form to display the record and what I am trying to do is get the text for that field to display in this color when viewing/editing this record. I can force it to a specific color without a problem but when I want it to use the color from the table it goes pear shaped.
    I have tried the following:
    Code:
    case(Color<>"","\"" +trim(color) + " on white\"",.T.,"black on white")
    In the expression editor this shows a result of "Rose on white" which is correct for the first record but when I exit the expression editor and then go back into it again the expression has changed to
    Code:
    case(Color<>"","\" on white\"",.T.,"black on white")
    I then changed it to include it in brackets as follows
    Code:
    case(Color<>"",("\"" +trim(color) + " on white\""),.T.,"black on white")
    This also appeared correct in the expression editor but on exiting and re-entering it, it has changed to
    Code:
    case(Color<>"","\""+chr(92)+"\"\"+trim on white\"",.T.,"black on white")
    Can anyone tell me what is going on and how I can get it to do what I want!

    Thanks

    David
    Tags: None
    #2
    Re: Color in a form

    You are probably confusing Alpha as well as me.

    What would be wrong with

    Code:
    case(Color<>"",trim(color) + " on white",.T.,"black on white")
    See if that sticks.
    There can be only one.

    Comment

      #3
      Re: Color in a form

      Hi Stan
      What you've suggested was my first attempt. That returned the following after exiting and then re-entering the Expression Editor
      Code:
      case(Color<>"","rim(color)+\" on white\"",.T.,"black on white")
      (My typing is bad, but not that bad but I checked it several times anyway!). The original expression shows the result as Rose on White (without inverted commas) so I thought that may have been the problem which is why I changed it.

      David

      Comment

        #4
        Re: Color in a form

        You don't need case().

        Code:
        color-" on white"
        is all you need.

        Comment

          #5
          Re: Color in a form

          But.. if you insist:
          Code:
          case(color<>"",color - " on white",.T.,"black on white")

          Comment

            #6
            Re: Color in a form

            The first option, without the CASE worked, thanks very much. If I include the CASE statement the expression still does funny things. I guess my main concern, given that I am evaluating Alpha with a view to future development, is why does the Expression Generator appear to parse it correctly in the first place? I would much prefer it tell me it's invalid or whatever at the time rather than finding it when testing and then have to revisit it. I actually included the CASE because using the genie set to a specific color generated that code which I then thought I could modify so suit my particular need.
            I have to say that the way it has handled (mishandled?) this fairly trivial piece of code worries me and makes the Expression Generator look a little flaky, which I sincerely hope is not the case because there is a lot that I do like about Alpha.

            David

            Comment

              #7
              Re: Color in a form

              I think what is happening is: you put the expression in the genie. Put the expression directly in the box that says "Color Equation".

              Comment

                #8
                Re: Color in a form

                Yes, you're right. If I use the CASE in the color equation it's fine. Because I don't know the syntax of a lot of these things I clicked on the Expression Generator button, which took me to the genie. From there I selected Expression Generator because the genie doesn't give you the opportunity to use a variable for the color and that's where my trouble started:( Once I know the syntax I can probably avoid a lot of these things.
                Thanks very much for your help.

                David

                Comment

                Previous template Next
                Working...
                X