Announcement

Collapse
No announcement yet.

[SOLVED]Global Variable Missing

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

  • [SOLVED]Global Variable Missing

    I created a multiple record form in SC 7 with a Where SQL search with global variable [category]. Run it, it asked for variable, i type it in. Then it says it is the global variable is missing.

    I do the same thing in SC 6 and it works perfectly???

    Unless something is new it must be a bug.

  • #2
    Hello,

    Have you set [category] output to "Out"?

    regards,
    Bernhard Bernsmann

    Comment


    • #3
      The variable must be set to "in" as we are wanting to select only those records that match the global variable [category].

      My understanding for global variable out is when you use it in other applications.

      this is the message i get

      The following global variables are missing: category;

      Seems to be a bug in sc7 as I get it to work perfectly in sc6

      Comment


      • #4
        I can be an error, haven't had the time to check it. But you need out in the application which creates the global variable. If you use in then it assumes that the global variable is created elsewhere and will look for the header variables or sessionvariables to find the variable. Here that is not the case so the global variable must be set to out. I useually advise to create *all* global variables in one spot, i.e. in the logon application if you have one. It prevents problems like these and it allows a better documentation in code.
        Albert Drent
        aducom software netherlands
        scriptcase partner, reseller, support and (turn-key) development
        www.scriptcase.eu / www.scriptcase.nl

        Comment


        • #5
          I set up the global variables as suggested. Made sure the settings are the same as SC6 and still get this....

          Comment


          • #6
            Hello Mr. Patterson,

            I believe the best way to find a proper solution on your case, is to send the application to our support. Our chat is active on workdays from 8:00am to 6:00pm, and our ticket system is always available.

            regards,
            Bernhard Bernsmann

            Comment


            • #7
              will do. Thanks for the great support. I really like scriptcase.

              Comment


              • #8
                Hello Mr. Patterson,

                I believe your issue was being caused due to a bug, which it was fixed on our last release. Please update your ScriptCase, and if the issue continues get in touch with our support.

                regards,
                Bernhard Bernsmann

                Comment


                • #9
                  Just updated and ran the app. Everything works! Consider this bug a dead one

                  Thanks

                  Comment


                  • #10
                    Thanks also for your feedback.

                    regards,
                    Bernhard Bernsmann

                    Comment


                    • #11
                      I just updated my scriptcase for the lastest release and the bug is back again.

                      Comment


                      • #12
                        I update the Feb 28 changes. Now the bug is back again

                        Comment


                        • #13
                          Hello,

                          I will check that with our bugs team.

                          regards,
                          Bernhard Bernsmann

                          Comment


                          • #14
                            I have the same problem on 7.00.0011

                            The problem 'goes away' if I change the form to a 'Single record' instead of any of the other choices...

                            Comment


                            • #15
                              Hello,

                              Issue reported to our bugs team.

                              Please update to 7.00.0012 and let me know if the issue continues.

                              regards,
                              Bernhard Bernsmann

                              Comment

                              Working...
                              X