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



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

Syntax issue with IF THEN ELSE

  • Filter
  • Time
  • Show
Clear All
new posts

  • Syntax issue with IF THEN ELSE

    I have the following code:

    END IF

    So far I have an error on line 5 possibly line 6. XBasic codes a bit differently than I was taught and that has been years ago so any help would be appreciated.


  • #2
    Re: Syntax issue with IF THEN ELSE

    Hi RJ,
    You don't say where you are using this code - is it on a button, a field rule or a form event? It looks like you want to change a field value based on the value of another field. You will need to include a pointer to the field objects either from the table or to the objects on the form.

    One example using the table pointer:

    dim tbl as p
    tbl = table.current()
      if tbl.payoer_id = tbl.consignee_id then
        tbl.prepaid_collect_tparty = "Prepaid"
      elseif tbl.payoer_id = tbl.shipper_id then
        tbl.prepaid_collect_tParty = "Collect"
        tbl.prepaid_collect_tParty = "Third Party"
      end if
    There is a bit more you may need to do dependent on where you are calling this script from - eg. test that the form/table is in view mode.
    Last edited by MoGrace; 06-03-2018, 11:14 AM.

    Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford


    • #3
      Re: Syntax issue with IF THEN ELSE

      I am using it on a lookup field.


      • #4
        Re: Syntax issue with IF THEN ELSE

        Ok so in field rules, instead of a lookup rule you need to set the conditional default values on the data entry tab. Also in your table structure, the field(s) you want to test should be before the field you want to fill and also on your form the tab sequence should follow that order too.

        in the prepaid_collect_tparty field rule

        [U]default [/U]    -   [U]condition[/U]
        "Prepaid"   -   payoer_id = consignee_id
        "Collect"   -   payoer_id = shipper_id
        "Third Party" - payoer_id <> consignee_id .and. payoer_id <> shipper_id
        Of course if Stan is watching, he may have a better way! - "There can be only one"
        Last edited by MoGrace; 06-03-2018, 12:53 PM.

        Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford


        • #5
          Re: Syntax issue with IF THEN ELSE

          I will give it a try and let you know. Thanks so much.


          • #6
            Re: Syntax issue with IF THEN ELSE

            Just another thought here...the default rules will only apply on a new record entry. If for some reason the comparison fields are not filled in before the record is saved, you may also want to define a simple list lookup rule for the prepaid_collect_tparty field. AND/OR you can add OnChange events for the consignee_id and shipper_id fields that will fill in the prepaid_collect_tparty field. I suppose it depends on how 'automatic' you want this fill-in to be.

            Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford


            • #7
              Re: Syntax issue with IF THEN ELSE

              Apparently I just over think these things.
              default - condition
              "Prepaid" - payoer_id = consignee_id
              "Collect" - payoer_id = shipper_id
              "Third Party" - payoer_id <> consignee_id .and. payoer_id <> shipper_id
              Worked perfectly.



              • #8
                Re: Syntax issue with IF THEN ELSE

                Just an option...

                	case tbl.payoer_id = tbl.consignee_id
                 		tbl.prepaid_collect_tparty = "Collect"
                	case tbl.payoer_id = tbl.shipper_id
                 		tbl.prepaid_collect_tparty = "Prepaid"
                	case else
                		tbl.prepaid_collect_tparty = "Third Party"
                end select
       is a great site to test and share sql code


                • #9
                  Re: Syntax issue with IF THEN ELSE

                  Thanks. I got that problem solved. Just one more to go and I'm finished. Just waiting on the criteria. I appreciate all the help.