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

mismatched fields

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

    mismatched fields

    Hi Phorum,

    On the onarrive event of a field named calc_multi, I have the following snippet:
    if(rnd_trp="Y",rnd_trip,1)

    rnd_trp is a character field
    rnd_trip is a numeric field = 2
    calc_multi is a numeric field

    Am I blind, this gives the error of mismatched fields.

    All help will be appreciated,
    efs

    #2
    RE: mismatched fields

    Ed,
    How have you defined calc_multi in field rules. If as a calculated field, the calculation must be supplied in field rules. If as a user entered field, then you must assign the value of the if statement to the field. Would be something like

    this.value=if(rnd_trp="Y",rnd_trip,1)

    Comment


      #3
      RE: mismatched fields

      Additional thought(s).

      You may be mixing form values with table values. You may need something like:


      this.value=if(rnd_trp.value="Y",rnd_trip.value,1)

      Comment


        #4
        RE: mismatched fields

        Hi Ohlen,
        Thank you for replying. I didn't use the field rules, I put the snippet
        on the onarrive event of calc_multi. I had hoped that this will
        eventually be a select/case function.

        Comment


          #5
          RE: mismatched fields

          Ed, Ohlen's question is a good one. Is 'Calc_Multi' a calculated display field on your form, or is it simply a normal text field object showing the value of a variable?

          Xbasic contains commands that permit you to talk to objects on the form. It also has commands that permit you to talk to the table beneath the form. We can't tell from your snippet what you're doing, because you haven't told us about the table fields, form fields, and variables that are in play here.

          If Calc_Multi is a calc field defined in the form you cannot assign a value to it directly, though you can refresh the field object on the form ( often not necessary).

          If Calc_multi is a simple variable, displayed in a field object also called 'Calc_multi' you can write to the variable, and then refresh the field object on the form, like this:

          var->Calc_multi = "Boo" 'assign value to variable
          :formname:Calc_multi.refresh() 'refresh object displaying variable on form

          Or,

          you can write straight to the field object on the form, like this:

          :formname:Calc_multi.value = "Boo"

          Notice that the syntax is different when writing to form objects, than when writing to variables directly.

          If the field object on the form has been renamed to something else, like 'object_name', then these examples become:

          var->Calc_multi = "Boo" 'assign value to variable
          :formname:Object_name.refresh() 'refresh form object

          and

          :formname:Object_name.value = "Boo"

          respectively.

          -- tom

          Comment


            #6
            RE: mismatched fields

            Hi Tom and Ohlen,

            Calc_multi is a simple "user entered" field in the table. The snippet
            is suppsed to set calc_multi to rnd_trp (which is 2 for this record)
            if rnd_trp is a "Y", if not to a 1.

            Comment


              #7
              RE: mismatched fields

              Ed, is it possible there's a fieldname typo in your script, just as there is in your last post? Otherwise, maybe it's time for you to post a working sample so we can see it?

              -- tom

              Comment


                #8
                RE: mismatched fields

                Hi Tom,

                OOPS, I left an "O" out of supposed. Usually I don't get typos on the fields because I drag them into the expression, my booboos are the garden variety of omitting parenz and hitting the period instead of the comma. Last night I changed calc_multi to a calculated field and inserted the following expression:
                if(rnd_trip="Y",rnd_trip,1) and it seems to be working. However this is merely a preliminary test to achieve the desired results. My hope is to replace the expression with a select/case since there are other values that can effect calc_multi.

                Question .... can a select/case of 6 or 7 cases be placed in a field rule expression? Since the differnt cases are usually different values, I am placing the largest value as the first case etc on to the smallest as the last. This should produce the largest proper value and omit the lower ones since select will close when it reaches a true value. It appears that I was not aware of the fact that I could not set the vaue of a user entered table level numeric field with an expression on the onarrive event. I am formulating the select/case now in MSWord for a copy and paste.

                I can not believe the patience people like yourself and others have with part time quasi developers like me. This forum is unbelievable.

                Thanks a million,
                efs aka ED

                Comment


                  #9
                  RE: mismatched fields

                  You can't use select .. case in a calculated field rule, you can use the case() function, limited to 16 pairs of expressions and results.
                  There can be only one.

                  Comment


                    #10
                    RE: mismatched fields

                    Ed, I was more concerned with the 'i' left out of rnd_trp.

                    -- tom

                    Comment


                      #11
                      RE: mismatched fields

                      Hi Stan,

                      Thank you, that saves me a lot of unnecessary work.
                      efs

                      Comment

                      Working...
                      X