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

Setting text in form

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

    Setting text in form

    I've created a generic form, called 'message'. I want to set the text heading and the text message from a button on another form through a UDF. The function is:
    Code:
    FUNCTION messages AS C (heading as c, message AS C )
    :form.view("Message","popup","center","center")
    :Message:txtHeading.Text = heading
    :Message:txtMessage.Text = message
    sleep(1)
    :Message:btnClose.Push()
    END FUNCTION
    When I push the button to send the actual text through the function I get an error:
    :Messages:txtHeading not found
    What have I written wrong?

    Thanks as always

    Les

    #2
    Re: Setting text in form

    My first thought is that you may not have the object names correct but you really don't elaborate on the structure of the form, Are there objects on the form with object names txtHeading and txtMessage?

    If so your code may run into a timing issue and you might try


    Code:
    FUNCTION messages AS C (heading as c, message AS C )
    form.load("Message","popup","center","center") 'leading colon not needed?
    :Message:txtHeading.Text = heading
    :Message:txtMessage.Text = message
    :Message.show()
    :Message.activate()
    sleep(1)
    :Message:btnClose.Push()
    END FUNCTION
    There can be only one.

    Comment


      #3
      Re: Setting text in form

      Originally posted by lcbarker View Post
      I've created a generic form, called 'message'. I want to set the text heading and the text message from a button on another form through a UDF. The function is:
      Code:
      FUNCTION messages AS C (heading as c, message AS C )
      :form.view("Message","popup","center","center")
      :Message:txtHeading.Text = heading
      :Message:txtMessage.Text = message
      sleep(1)
      :Message:btnClose.Push()
      END FUNCTION
      When I push the button to send the actual text through the function I get an error:

      What have I written wrong?

      Thanks as always

      Les
      It may be in your function type. You are declaring massages as C and then in the function are not setting messages to anything. I think the function is trying to return character value. You might try
      Code:
      FUNCTION messages AS [B][COLOR=Red]V[/COLOR][/B] (heading as c, message AS C )
      The V type stands for void and is used when you just want to do stuff with out returning anything in particular.

      WARNING. This just a guess.
      Tim Kiebert
      Eagle Creek Citrus
      A complex system that does not work is invariably found to have evolved from a simpler system that worked just fine.

      Comment


        #4
        Re: Setting text in form

        Les, double check the names of the text objects in your form layout. The object names must match the names used in your function.

        Comment


          #5
          Re: Setting text in form

          Thanks guys for thinking with me. I tried all your suggestions but they didn't work. You at least helped me realize I wasn't crazy with this. I did finally get it to work, and here's how. It was strange.

          I knew the object names were correct because I had 'copied to clipboard' from the object explorer. But, just to make sure I went back again to double check. In the 'Open Layout Windows' dropdown I found a bunch of open forms that I had never created: :center, :center0, :center1, etc. I thought, where'd they come from.

          So I decided to test it from a clean slate and started a new db with new dummy tables and a new calling form. I copied over the message form and the messages function. Tried it out a couple of times and it wouldn't work. So I opened the object explorer and here were a couple more "center" forms. Weird.

          So I went back to the original db. And deleted the "center","center" from the form view command (only reference to center that I knew of) and the function stopped making the :center forms. Isn't that strange! The "center" commands, or at least one of them, was creating a new form in memory which was being called instead of the message form.

          Then the function began to work, at least somewhat. I made modifications until it did. I assigned the parameters passed in the function to shared variables and assigned them to the text boxes in the oninit event in the message form. The code is here:
          Code:
          FUNCTION messages AS v (heading as c, message AS C )
          dim f as p	
          dim shared vcFormCloseMessage as c
          dim shared vcFormCloseHead as c
          
          vcFormCloseHead = heading
          vcFormCloseMessage = message	
          f = form.view("Message","popup")
          sleep(2)
          :Message:btnClose.Push()
          :PersonInfoDisplay.close()
          END FUNCTION
          Thanks again for your willingness to help. It helped me learned some new nuance to Alpha.

          Les

          Comment


            #6
            Re: Setting text in form

            Les,

            This is the syntax for Form.view from the help
            <FORM> as P = FORM.VIEW( Form_Name as C [, Style as C [, Window_Name as C [, Horizontal_Position as N [, Vertical_Position as N ]]]] )
            Notice the parameter called Window_Name. According to the docs this is nolonger applicable. However in order to use the position parameters you still need to supply the Window_name Parameter as "" so your command should have been
            Code:
            :form.view("Message","popup",[COLOR=Red][B]"",[/B][/COLOR]"center","center")
            The way you had it the first Center was being used as the Window name.
            Tim Kiebert
            Eagle Creek Citrus
            A complex system that does not work is invariably found to have evolved from a simpler system that worked just fine.

            Comment


              #7
              Re: Setting text in form

              Just a followup on the form view command. The command in the help file says
              FORM.VIEW( Form_Name as C [, Style as C [, Window_Name as C [, Horizontal_Position as N [, Vertical_Position as N ]]]] )
              When I had originally written the function I had
              Code:
              form.view("Message","popup",,"center","center")
              because I thought I needed to allow for the middle parameter in the nested sequence. But it gave me an error message saying parameter missing, or something, so I took out the comma. Thus the command was reading that the first 'center' was actually the 'window name', and because it didn't exist on the hard drive it created it in memory. But since it was fictional it didn't have the text boxes to refer to, and so I kept getting the not found message.

              Since I was curious about this I modified the function to read
              Code:
              form.view("Message","popup","Message","center","center")
              . Now it's referencing the 'Message' window, which does exist, and so the 2 center positioning commands work fine.

              Love these puzzles, don't you.

              Les

              Comment


                #8
                Re: Setting text in form

                Tim,

                Looks like we tied.

                As you can see that was my original thinking, but got an error message. Not sure what you're really supposed to do, but to be safe you should add the window name anyways.

                Thanks again.

                Les

                Comment


                  #9
                  Re: Setting text in form

                  Originally posted by lcbarker View Post
                  Tim,

                  Looks like we tied.

                  As you can see that was my original thinking, but got an error message. Not sure what you're really supposed to do, but to be safe you should add the window name anyways.

                  Thanks again.

                  Les
                  Great minds think a like.... and don't bother with the other half of that saying.

                  I missed it until your previous post. The same is true for many functions where you use an optional parameter. You still need to enter the optional parameters up to the one you are using even if just an empty string or what ever the type is. Because the function will look for the info that belongs in a particular position.
                  Tim Kiebert
                  Eagle Creek Citrus
                  A complex system that does not work is invariably found to have evolved from a simpler system that worked just fine.

                  Comment


                    #10
                    Re: Setting text in form

                    Tim,

                    Just for fun I typed "" into the middle of that string instead of "Message" and it worked fine.

                    Thanks again

                    Les

                    Comment

                    Working...
                    X