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

Variable not changing

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

  • Variable not changing

    I created a variable account.
    On the event oninit I pass the value acctount_no to the variable Vaccount
    dim global Vaccount as C
    Vaccount = this:Account_no.value.
    When I change records, the variable doesn't change.

  • #2
    onfetch
    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

    Comment


    • #3
      I tried it, didn't work..
      In the form variables I have : Vaccount = ""
      Onfetch I have Vaccount = Account_No
      ON Init I have dim global Vaccount as C
      Vaccount = this:Account_no.value

      II put the Vaccount on the form, it gets the first account, but it stays there when I goto the record.

      Comment


      • #4
        Originally posted by rlgiordano View Post
        I tried it, didn't work..
        In the form variables I have : Vaccount = ""
        Onfetch I have Vaccount = Account_No
        ON Init I have dim global Vaccount as C
        Vaccount = this:Account_no.value

        II put the Vaccount on the form, it gets the first account, but it stays there when I goto the record.
        be consistent in calling all the variables global.

        Dim them in each event and leave out the form variable.

        pack the form's table/set dictionary to get rid of old code.

        ________
        Put these code in each event and where you are using the variable(s) to see what is happening to the variables.

        a5_show_variable(local_variables() , "Currently Defined Local Variables")

        a5_show_variable(global_variables() , "Currently Defined Global Variables")
        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

        Comment


        • #5
          I thought once you declared it uin global, then it should be their in all the time.
          So which event do I declare it I am going from the primqry form to a report form to select what report tp print/preview.
          Which event would it put :a5_show_variable(local_variables() , "Vaccount")

          Comment


          • #6
            Originally posted by rlgiordano View Post
            I thought once you declared it uin global, then it should be their in all the time.
            So which event do I declare it I am going from the primqry form to a report form to select what report tp print/preview.
            Which event would it put :a5_show_variable(local_variables() , "Vaccount")
            dim it global everywhere you use it.

            put that code about the variables in everywhere you are assigning the variable so you can see what is going on.

            Once you've solved the issues, then remove the code for showing variable values and scope.
            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

            Comment


            • #7
              Bob, if memory serves (so to speak), Alpha permits you to use the same name for variables in local, shared, and global spaces. Three different variables. All with same name. Best practice is to dim globals whenever used to be sure Alpha is not picking up a local or shared by mistake.

              Comment


              • #8
                Hi om, I have'n forgotten about you,
                I declare the variable in the oninit event:

                dim global Vaccount as C
                Vaccount = this:Account_no.value

                I don;t know were to put:
                a5_show_variable(global_variables() , "Vaccount")
                from primary form to report menu, then select the report to print.
                Something so simple yet, but making me go crazy
                I guess my problem is not knowing exactly what each event pertains to.

                Comment


                • #9
                  Originally posted by rlgiordano View Post
                  Hi Tom, I haven't forgotten about you,
                  I declare the variable in the oninit event:

                  dim global Vaccount as C
                  Vaccount = this:Account_no.value

                  I don't know were to put:
                  a5_show_variable(global_variables() , "Vaccount")
                  from primary form to report menu, then select the report to print.
                  Something so simple yet, but making me go crazy
                  I guess my problem is not knowing exactly what each event pertains to.
                  That's why you put the code in each event so you can see when that event happens and what the variables are set to.

                  have this code in each event.
                  OnInit
                  OnFetch
                  ____________________________
                  dim global Vaccount as C
                  Vaccount = this:Account_no.value

                  a5_show_variable(local_variables() , "Currently Defined Local Variables")
                  a5_show_variable(global_variables() , "Currently Defined Global Variables")
                  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

                  Comment


                  • #10
                    I am going to ask a stupid question.
                    Do I have to put the variable in the line.

                    dim global Vaccount as C
                    Vaccount = this:Account_no.value
                    a5_show_variable(local_variables() , "Vaccount")
                    a5_show_variable(global_variables() , "Vaccount")

                    Comment


                    • #11
                      Originally posted by rlgiordano View Post
                      I am going to ask a stupid question.
                      Do I have to put the variable in the line.

                      dim global Vaccount as C
                      Vaccount = this:Account_no.value
                      a5_show_variable(local_variables() , "Vaccount")
                      a5_show_variable(global_variables() , "Vaccount")
                      No

                      Please try what someone sends you and then report back the results.
                      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

                      Comment


                      • #12
                        Bob, explain again what you are trying to do, please.
                        Ted Giles
                        Example Consulting - UK
                        .

                        sigpichttp://ec12.example-software.com//
                        See our site for Alpha Support, Conversion and Upgrade.

                        Comment


                        • #13
                          What's the resolution of this?
                          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

                          Comment


                          • #14
                            I connected with Bob and believe he has this resolved. Using onFetch to assign the "next" field value to the variable seemed to do the trick.

                            Comment


                            • #15
                              Originally posted by Tom Cone Jr View Post
                              I connected with Bob and believe he has this resolved. Using onFetch to assign the "next" field value to the variable seemed to do the trick.
                              Tom

                              Thanks for the follow up so future travelers know how to resolve this.
                              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

                              Comment

                              Working...
                              X