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
Devcon 2020 Goes Virtual! LEARN MORE >

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

Refering to controls on form in xbasic

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Refering to controls on form in xbasic

    Refering to controls on form in xbasic

    --------------------------------------------------------------------------------

    I want to get a value of a specific control on the active form from xbasic. Is this possible?

    Mike
    Tags: None
    #2
    Re: Refering to controls on form in xbasic

    What is the context? Alpha form coding relates to events.

    The proper syntax for referring to a control's value is

    objectname.value

    where objectname is revealed by examining the control's properties. The objectname is usually the same as the underlying table field name, variable name, etc but it may differ.
    There can be only one.

    Comment

      #3
      Re: Refering to controls on form in xbasic

      Thanks I'm new to xbasic, I am used to VBA. I could not find the syntax.

      currentform.controlname.value is this the syntax?

      Comment

        #4
        Re: Refering to controls on form in xbasic

        I believe the format is...

        :formname:controlname.text

        or

        :formname:controlname.value

        Comment

          #5
          Re: Refering to controls on form in xbasic

          Mike,
          I'm going to give you a headstart I never got!! After a month or so when first using Alpha and wondering how the hey people were easily figuring out the syntax/object names, I ran across the Object Explorer....Top Menu-->View-->Object Explorer. You can see everything on your form/browse and either find it from this dialog or use the copy to clipboard to see a form of syntax to use in referring to the objects.
          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

            #6
            Re: Refering to controls on form in xbasic

            Mike --

            Here's another suggestion. Presumably there is an event that will cause your program to get the value of an object on your form. Create a new action script, select Objects Properties (Set & Get), select Get 'Value' property of Object. After you have created the action script, if you still want to know how to reference the object in Xbasic, look at the Xbasic underlying the Action Script to see how it was done.

            -- Dick James

            Comment

              #7
              Re: Refering to controls on form in xbasic

              Definitely---and that is most assuredly the next step for anyone who wants to dive deeper into xbasic....Gets interesting too once you see how much "fluff" Alpha has to put into the xbasic behind the scenes for Action Scripts to work as they do.
              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

                #8
                Re: Refering to controls on form in xbasic

                Thanks for the help, that works great. I spent 8 hours yesterday trying to figue this out on my own.

                Comment

                  #9
                  Re: Refering to controls on form in xbasic

                  And now I'll throw in another twist.

                  Be very careful when using <Object_name>.value. This works fine when dealing with character fields and, I think, with date fields. However, there are some strange things that can happen when dealing with numeric and logical fields.

                  DISCLAIMER: These issues may or may not apply to the current build. Some of these issues may have been fixed but they all did exist at some point in earlier versions.

                  1. When getting the "<Object_name>.value" of a numeric field when the actual field value is empty (null), the value returned is some huge number like X*10^123. So, testing to see if it is zero only works when it is not blank. (In some cases this can be a good thing - just be aware of it.)

                  2. When getting the "<Object_name>.value" of a logical field when the actual field value is empty (null), the value returned is .T. Obviously most people would expect it to be .F.

                  3. I'm not sure what it was but I know that I had some problems with reading the .text value of a numeric field. It's very possible that it was only the fact that you can't just use val( <Object_name>.text ) to get the actual value because the val() of a blank field is still zero. So, if you want to test for a blank field, you have to either test for .text being blank or .value being huge.

                  As a result of dealing with the above problems in the past, my current philosophy is that all numeric and logic fields will ALWAYS have a default value - especially logical fields. Even if I restructure a table in a generic app through a routine in the autoexec script, I will include as part of that routine a section that enters the default value in the existing records. The one exception would be the rare case where it's necessary to allow a numeric field to be blank in order to determine if a value was ever entered. (Yes, a value of zero could be a valid entry.)

                  Comment

                  Previous template Next
                  Working...
                  X