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

field reference confusion

  • Filter
  • Time
  • Show
Clear All
new posts

    field reference confusion

    I would like to set the value of a field on a form to a certain value, based on it's user-entered value. In this example, a survey has certain values which are re-coded from 1 to 0 or vice versa. This script will run with the form open.

    Do I reference the form field by:

    :frm:field = 0

    :frm:field.value = 0 ?

    Thank you.
    David A. Volgas, MD

    Re: field reference confusion

    I guess, more specifically, if my parent form is MFA,

    if :MFA:Move4.value = 1 then
    :MFA:Move4.value = 0
    :MFA:Move4.value = 1
    end if

    --- or ---

    if :MFA:Move4 = 1 then
    :MFA:Move4 = 0
    :MFA:Move4 = 1
    end if

    David A. Volgas, MD


      Re: field reference confusion


      Reading values for fields on the form you should use your first example


      You probably would have to issue a parentform.refresh_layout() also.

      Is this code on a button?

      Tom Baker
      Last edited by Tbaker; 01-31-2010, 01:24 PM. Reason: added


        Re: field reference confusion


        Put the form in design mode

        click on the object on the form

        view - object explorer

        Now you can see all of the references to that object.

        Click the button Copy to Clipboard - I use the relative name
        Al Buchholz
        Bookwood Systems, LTD
        Weekly QReportBuilder Webinars Thursday 1 pm CST

        Occam's Razor - KISS
        Normalize till it hurts - De-normalize till it works.
        Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
        When we triage a problem it is much easier to read sample systems than to read a mind.
        "Make it as simple as possible, but not simpler."
        Albert Einstein


          Re: field reference confusion


          Always forget to give advice on using Object Explorer - which I use all the time. I guess I use it so much if has become second nature.

          Getting old.

          Tom Baker


            Re: field reference confusion

            Guys, thank you. Tom, this script is on a button, and i do use a parentfrom.refresh at the end.

            One other question is .. do I need to open the table underlying the form in my xbasic script at all? Can I just reference the fields as above and let A5 handle whether I'm in change mode or enter mode?

            David A. Volgas, MD


              Re: field reference confusion


              As long as you are referencing a field that is on the parentform, yes alpha will handle it whether it is a new record or a change but to be safe (and if the entry is complete)

              If the form is in enter mode, after the button is pushed the form should remain in enter mode so you would need to issue a parentform.commit(). If it is change mode then the parentform.commit() would not be necessary but I would use it anyway.

              Also parentform.refresh() should show an error message - I am sure you meant parentform.refresh_layout() or parentform.refresh_fields().


                Re: field reference confusion

                Thank you, Tom.

                I get confused between when to address the table directly and when to address the form fields.

                David A. Volgas, MD


                  Love version 10!!!

                  Let me just say, having really struggled with version 9, version 10 rocks! very stable ... now, when I have a problem, I know it's me - not the program.

                  Congratulations to Richard and crew. And thanks for making development fun again!

                  David A. Volgas, MD