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

caps vs. lower case

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

    caps vs. lower case

    I want "The Brown Dog" to flag as NOT equal to "the brown dog".

    I am comparing the contents of fields in separate tables. One table holds the correct capitalization I need to update those that are not equal.

    #2
    RE: caps vs. lower case

    If("The Brown Dog" == "the brown dog",.T.,.F.)
    Peter
    AlphaBase Solutions, LLC

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


    Comment


      #3
      RE: caps vs. lower case

      Are you saying that the data in the two fields is equal other than the capitalization. If so, why not update all of them by operation or rule. There are built in functions for most capitalization requirements, upper(), f_upper, and w_upper. W_upper(yourfieldname) will capitalize each word in a field.

      If the field is correct as is, the operation or rule will not change it.
      There can be only one.

      Comment


        #4
        RE: caps vs. lower case

        Currently, one table has the 'correct' capitalization as (not just Upper Lower, but fixed for The's in the middle etc. and some foreign words de, la, etc.).

        I didn't want to run an update operation, but rather have an opportunity to eyeball any of them that are not equal, and skip some, and change some.

        i.e. BSJM Dissertations needs to be capped this way, but a field rule would make it Bsjm Dissertations, unless I added it to the exceptions file. I have too many odds and ends to get them all in an exceptions file.

        Comment


          #5
          RE: caps vs. lower case

          I think your expression would evaluate to true, and I would want it to be false.

          At least in using my field names:
          FIXING_LIST->Match GOOD_JT->JTTitle
          different capitalization does not make this one true

          Comment


            #6
            RE: caps vs. lower case

            No, the expression evaluates to be false.

            == NOT =
            Peter
            AlphaBase Solutions, LLC

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


            Comment


              #7
              RE: caps vs. lower case

              Valerie, I agree with Peter on this one.

              From the interactive editor, it's easier to see the two equals signs:

              ?if("The Brown Dog" == "the brown dog",.t.,.f.)
              = .F.



              A double equals means 'exactly equal'.


              -- tom

              Comment


                #8
                RE: caps vs. lower case

                I'd never seen the == notation before. I have only ever used .

                I see from Tom's post that it means exactly equal. But, why does it register a different answer than ?

                Most of the records I am dealing with are 'exactly equal' (or should be).

                Can I place a "not" around the whole thing?

                Here is my current code.
                IF FIXING_LIST->Match GOOD_JT->JTTITLE THEN
                SELECT

                Comment


                  #9
                  RE: caps vs. lower case

                  Gues what I found in the help file:

                  When comparing strings, the Not Equal () and Not Exactly Matching (!=) operators differ slightly. The Not Equal operator is not case-sensitive and removes any trailing blanks before the strings are compared. The Not Exactly Matching operator compares both strings including trailing blanks and is case-sensitive.

                  I never would have even looked for it without your help with the ==.

                  THANKS!!

                  Comment


                    #10
                    RE: caps vs. lower case

                    Aren't help files wonderful!

                    Also, check out the "Improved Capitalization Checker" on the www.learn alpha.com site. This was designed just for your situation. If you like the idea, let me know as I have an updated version which checks for a few more situations.

                    Comment


                      #11
                      RE: caps vs. lower case

                      Let's try again:

                      the not exactly matching idea didn't work.

                      IF FIXING_LIST->Match != GOOD_JT->JTTITLE THEN
                      . . .
                      Match had "Hemostase"
                      JTTitle had "hemostase"
                      The above statement did not evaluate to true.

                      IDEAS??

                      My comparison of the two fields allows the user to make changes to the good_jt (a lookup table) and then update records in the fixing list without updating all 13,000 records.

                      Comment

                      Working...
                      X