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

<Field>.Value_Put()

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

    <Field>.Value_Put()

    I have on a form 2 fields: Bill_Add and Ship_Add, and a button. As an exercise, I am trying to write a very simple script attached to the button to set the value in Ship_Add = to Bill_add. I tried to learn something from the Xbasic code generated by The Set Field Value Action script, but got lost in the details. I then tried the <Field>.Value_Put() method with no result.
    Could someone please show me a simple Xbasic script to do this?
    Thanks

    #2
    Re: &lt;Field&gt;.Value_Put()

    Gaby,

    Go into Design Mode.
    On the top menu click on View-->Object Explorer. Find your first field. click on Copy to Clipboard. Choose relative and the one that has .value added to it. On your button's OnPush event, choose action scripting then choose xbasic from the left screen and Inline xbasic from the right screen. ,,Or just choose the xbasic editor instead of action scripting.

    when in editor, right click and paste or use control+V.

    It should look something like topparent:Ship_Add.value

    go back to the Object explorer and do the same for the second field.

    add this to what you already pasted in the editor like so

    topparent:Ship_Add.value = topparent:Bill_Add.value


    For others who want Action Scripting....
    You could also do this via Action Scripting in various ways. One would be by choosing Objects Properties (Set and Get) on the left screen and Set Properties of Objects on the right screen. Then choose you field in the top box, choose the Value from the second box and then choose Specify and expression.... from the drop down--in the expression builder choose what you want the field chosen to equal.
    Mike
    __________________________________________
    It is only when we forget all our learning that we begin to know.
    It's not what you look at that matters, it's what you see.
    Henry David Thoreau
    __________________________________________



    Comment


      #3
      Re: &lt;Field&gt;.Value_Put()

      Fantastic; Thanks Mike :)

      Comment


        #4
        Re: &lt;Field&gt;.Value_Put()

        Gaby,

        Xbasic includes commands that talk to tables "beneath" the form, and commands that talk to the table "through" the form. Mike's approach talks to the table "through" the object on the form. This simulates the user entering the desired field value from the keyboard.

        The first example in the help file discussion of <field>.value_put() illustrates how to talk directly to the table beneath the form. After running the example script you'd need to refresh the field object to see the new value.

        Comment


          #5
          Re: &lt;Field&gt;.Value_Put()

          Tom: your explanations clarified a lot of things for me. Why are these details not clearly mentioned somewhere in the user guide or did I missed something?

          Comment


            #6
            Re: &lt;Field&gt;.Value_Put()

            To make it even more confusing, I'd almost never use the ".value_put()" command because it's almost never necessary. As far as I'm concerned, its only use is when looping through fields in some generic routine - probably for some type of application utility (which I've built a few of). In the vast majority of cases, it's much easier just to get a pointer to the table and use the field names.....

            tc = table.current() [or tc = table.get("<tablename>")]
            tc.change_begin()
            tc.ship_add = tc.Bill_add
            tc.change_end()

            After which you may need to use a parentform.Refresh_layout() to see the change. (or may not - I simply don't recall.)

            HOWEVER, if you are changing a field that is shown in the current form, it's probably best to use the form methods. Otherwise you can run into problems. For example, my above script would cause an error if you tried to run it while the form was already in data entry mode while Mike's code that uses form methods would not. All Mike's code would do is put the form into data entry mode IF it was in View mode before that script ran. If the form was already in Enter or Change mode, it would just change another field.

            Comment

            Working...
            X