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

what's wrong with this equation?

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

    what's wrong with this equation?

    dim pn as c
    pn="SKU321 "
    if(substr(pn,1,3)="SKU",pn=rtrim(substr(pn,4,30)),pn=pn)
    ?pn
    = "SKU321 "

    I want to run an update that says
    If the first three letters of "PN" are "SKU" then pn=the remainder of the part number without the SKU otherwise leave the pn alone.

    If substring of pn starting at the first letter, ending at the 3rd letter is SKU then the part number is equal to pn starting at the 4th letter going to the 30th letter but trim trailing blanks OR leave pn equal to pn.

    As you can see from the above, I get the complete pn no matter what.
    Jim Belanger

    #2
    Re: what's wrong with this equation?

    Code:
    dim pn as c
    pn="SKU321 "
    ?if(left(pn,3)="SKU",substr(pn,4,30),pn)
    = "321 "

    Comment


      #3
      Re: what's wrong with this equation?

      If you want to know why yours does not work, is because:
      if(substr(pn,1,3)="SKU",pn=rtrim(substr(pn,4,30)),pn=pn)
      ?pn=rtrim(substr(pn,4,30))
      = .F.


      ?pn=pn
      = .T.

      So, what will the expression: if(substr(pn,1,3)="SKU",pn=rtrim(substr(pn,4,30)),pn=pn) produce?
      a logical output, .T. or .F.

      The value of pn has not changed since you dimmed it, so:
      ?pn
      = "SKU321 "

      Comment


        #4
        Re: what's wrong with this equation?

        I must be thick!!

        dim pn as c
        pn= "sku321 "
        if(left(pn,3)="sku",substr(pn,4,30),pn)
        ? pn
        = "sku321 "

        so I tried this

        if(left(pn,3)="sku",pn=substr(pn,4,30),pn=pn)
        ? pn
        = "sku321 "
        Jim Belanger

        Comment


          #5
          Re: what's wrong with this equation?

          If you want to know why yours does not work, is because:
          if(substr(pn,1,3)="SKU",pn=rtrim(substr(pn,4,30)),pn=pn)
          ?pn=rtrim(substr(pn,4,30))
          = .F.

          ?pn=pn
          = .T.

          Why doesn't the equation pn=substr(pn,4,30) change the part number?
          Jim Belanger

          Comment


            #6
            Re: what's wrong with this equation?

            Code:
            dim pn as c
            pn= "sku321   "
            [B]pn=[/B]if(left(pn,3)="sku",substr(pn,4,30),pn)
            ?pn
            = "321   "
            Last edited by G Gabriel; 07-13-2008, 03:28 PM.

            Comment


              #7
              Re: what's wrong with this equation?

              Originally posted by Beltronics View Post
              Why doesn't the equation pn=substr(pn,4,30) change the part number?
              You think you are telling alpha MAKE pn EQULAS substr(pn,4,30), but that's not the case. You are telling alpha the left side of the equation eqauls the right side. It's the difference between a command and a statment:

              Make all men equal: Command
              All men created equal: statment.

              And the statment in this case is false.

              The second statment: pn=pn is true
              as in 1=1.

              If you want to change it to a command, you say:
              pn=If(.........., this value, other value)
              i.e.
              if the condition is true, make pn equals the true statment (first statment after the condition), if not true, make it equal the false statment.
              Last edited by G Gabriel; 07-13-2008, 03:35 PM.

              Comment


                #8
                Re: what's wrong with this equation?

                OK, that last one you sent does what I want.
                I thought that the if-then statement was

                if (this is true, do this, if not do that)
                That's what I was trying to work with.

                With your latest version (which I understand) if the pn does not begin with sku it gets ignored. as below

                dim pn as c
                pn= "sk321 "
                pn=if(left(pn,3)="sku",substr(pn,4,30),pn)
                ?pn
                = "sk321 "


                Now, if I could get the Part_ID thing to work, I'd call it a weekend!
                Jim Belanger

                Comment


                  #9
                  Re: what's wrong with this equation?

                  Originally posted by Beltronics View Post
                  With your latest version (which I understand) if the pn does not begin with sku it gets ignored. as below
                  Isn't that what you want?

                  Comment


                    #10
                    Re: what's wrong with this equation?

                    It certainly is. I just ran it that way to make sure it did. No, it works fine. Thank you, have a beer, on me! When I put this in an operation to run, I had to remove the pn= at the beginning; (and I know why) which is what I was trying to do to begin with.
                    Jim Belanger

                    Comment

                    Working...
                    X