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

Xbasic Clarity Please

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

    Xbasic Clarity Please

    I became interested in this as a result of Howard Reisdorf's post. Following the instructions on pgs 200 & 201 of the Xbasic Reference Manual, value_get(), I created a test field called "testingvalue" and on this field's OnArrive event, I entered the example in the manual as follows:

    tbl=table.current()
    fld=tbl.field_get("lastname")

    "lastname" is an actual field in the current table so the example in the manual and real life field name is the same.

    I get the error message "No such field" when testing in the Interactive tab and when running the actual test, the value of the lastname field is not put into the "testingvalue" field either when the "testingvalue" field gets or loses focus.

    I understand this code to take the value of the lastname field and put it in the testingvalue field. (both fields are in the same table) What am I missing here?

    Thanks,

    kenn
    TYVM :) kenn

    Knowing what you can achieve will not become reality until you imagine and explore.

    #2
    RE: Xbasic Clarity Please

    If your interest is in getting the value for a field, here's a script that works well:

    tbl=table.current()
    value=tbl.message

    ui_msg_box("",value)

    In this case, my field is was MESSAGE. I put the message box to confirm that it was working properly.

    Comment


      #3
      RE: Xbasic Clarity Please

      You didn't post all your code so it's hard to see exactly what you want. TGhe part you did post just obtains two pointers "tbl" and "fld". The example you quote goes on:

      For example, these statement are all equivalent:
      tbl = table.current()
      fld = tbl.field_get("lastname")

      These are three different, but equivalent, ways to store the field value to a variable:


      name = customer->last_name
      name = tbl.lastname - this one based on the "tbl" pointer obtained above
      name = fld.value_get() - this one based on the "fld" pointer obtained earlier
      There can be only one.

      Comment


        #4
        RE: Xbasic Clarity Please

        Hi Stan,

        Thank you for your input. The example in the book is confusing for a novice Xbasic user. It states:

        For example, these statement are all equivalent:

        tbl = table.current()
        fld = tbl.field_get("lastname")

        name = customer->last_name
        name = tbl.lastname
        name = fld.value_get()

        Interpretation:
        Should it read: these statement(s) or should it read: this statement? I took it to mean 'these statements' but then my question was, where does one draw the line between one statement and the other? What all must be included in the statement?

        A novice will also ask, what does the word 'name' represent? A field in the current table? A field where the value is to be placed? The word 'name' wasn't mentioned before so a novice is left pondering what it references.

        Perhaps the manual could have explained that the first 2 lines are necessary pointers and one of the last three lines must be added. A complete example would have been useful.

        Can't wait to get to v5 and a manual that is "novice user friendly".

        Again , this isn't something I'm needing to work with but a novice can spend a lot of time trying to intrepret a not so good written manual.

        Thanks, Stan for your insight.

        kenn
        TYVM :) kenn

        Knowing what you can achieve will not become reality until you imagine and explore.

        Comment


          #5
          RE: Xbasic Clarity Please

          The examples in this thread are xbasic. I started with using action scripting, which I thought, did all of the code for you. When I did convert the action scripting to xbasic it came out with a single line of code (that didn't work either). My question is: "Why doesn't action scripting set this up for the user?" (add "correctly")
          Howard

          Comment


            #6
            RE: Xbasic Clarity Please

            I've complained often enough about the manual, as have others. I gave up hoping for a rewrite.

            Probably the most simple restatement would be:

            For example, these statements are all equivalent in assigning a field named "lastname"'s value to a variable named "name":

            'using table name
            name = customer->last_name

            'using table pointer alone
            tbl = table.current() 'obtain table pointer
            name = tbl.lastname

            'using table and field pointers
            tbl = table.current() 'obtain table pointer
            fld = tbl.field_get("lastname") 'obtain field pointer
            name = fld.value_get()

            I look forward to a good manual as well.

            Signed: a novice Xbasic user, as well
            There can be only one.

            Comment


              #7
              RE: Xbasic Clarity Please

              Ken,

              if you put
              tbl=table.current()
              fld=tbl.field_get("lastname")

              in the interative window, it won't give you
              the results you expect, because table.current() is not the
              form's table in the interactive window.

              if you want to set the value of your "testingvalue" field in the OnArrive event of the field on a form, try this:

              this.text=table.current().lastname
              this.refresh()

              Comment


                #8
                RE: Xbasic Clarity Please

                Hi Peter,

                Works like a charm!!!

                Thanks,

                kenn
                TYVM :) kenn

                Knowing what you can achieve will not become reality until you imagine and explore.

                Comment

                Working...
                X