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

Current Form or Another Form

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

  • Current Form or Another Form

    Hi there,

    I use the Form-Duplication facility to avoid having to rebuild Forms. Once the Form is duplicated
    Once the Form is duplicated i make appropriate amendments to the resultant Form as follows

    3)
    'DEBT_XACT_CRN_M' Last Duplicated - (CRN to use as Master due to Alloc present)
    'DEBT_XACT_INV_M' Sep 5 2016 14:04hrs
    'DEBT_XACT_PAY_M'
    'DEBT_XACT_JRN_M' May 24 2016 8:17am

    After duplicating 'Debt_Xact_Crn_m' to 'Debt_Xact_Inv_m' (and others) do the following
    a) Edit Form Properties
    Window caption 'Debt_Xact_Inv_m'
    Backdrop colour
    Filter/Order Filter Expression - Trde_Xact_Nom->Tn_Xact5f = "INV"

    ..together with others including "Customise" buttons (many) and certain Scripts.

    It has become a real mission to "Customise" the buttons on a form every time I make Form amendments
    to the Master 'DEBT_XACT_CRN_M'

    One problem that I have is a concern when running common Functions within these "identical" Forms, that each
    individual Form retains its own Shared variables values when running concurrently, witout cross-pollination from
    any other Form.

    I need your opinion as to whether Alpha5 Form is solid enough to retain these Shared Variables if I rely on
    'Current Form Window' rather than having to alter each instance to 'Another Form Window'. 'Another Form Window'
    to my mind will give additional insulation against the Shared Variables becoming corrupt.

    When testing these "Identical" forms with ''traceln' when 'Current Form Window' was retained
    the Shared Variables seemed in some instances to cross-pollinate ! If I am interpreting correctly

    Trusting that my explanation is clear. Maybe there is a better way ?

    Looking Forward
    Dave Mac

    It's not so much what you don't know that gets you into trouble, but what you know for sure, that just ain't so. - Mark Twain.

  • #2
    Re: Current Form or Another Form

    If you are asking whether session variables (shared) can communicate between forms I think the answer is yes. The documentation says


    Variable exists while ?

    Session
    SHARED

    (e.g. dim SHARED NAME as C )
    A window is open. Even if you change the layout that is loaded in the window (by using the File > Open? command from within the Form or Browse window), the variable continues to exist.
    There can be only one.

    Comment


    • #3
      Re: Current Form or Another Form

      Originally posted by Stan Mathews View Post
      If you are asking whether session variables (shared) can communicate between forms I think the answer is yes. The documentation says


      Variable exists while ?

      Session
      SHARED

      (e.g. dim SHARED NAME as C )
      A window is open. Even if you change the layout that is loaded in the window (by using the File > Open? command from within the Form or Browse window), the variable continues to exist.
      Thanks for the input, Stan.

      What specific documentation are you referring to ?

      I am more interested in shared variables only being available (scoped) within the named window and not being accessible
      within the re-named duplicate window.

      Have a good one
      Dave Mac

      It's not so much what you don't know that gets you into trouble, but what you know for sure, that just ain't so. - Mark Twain.

      Comment


      • #4
        Re: Current Form or Another Form

        In the local documentation it is under the heading Variable Scope.

        Seems like you want....

        Layout Cannot be declared using Xbasic The layout is open. If a different layout is loaded in the
        window (by using the File > Open? command from
        within the Form or Browse
        window), the variable will disappear.
        There can be only one.

        Comment


        • #5
          Re: Current Form or Another Form

          Originally posted by Stan Mathews View Post
          In the local documentation it is under the heading Variable Scope.

          Seems like you want....

          Hi Stan,

          Thanks for your reply.

          If you are wondering why it takes me so long to respond to your help, it is because
          it is a real mission to connect to Alpha Message Board. It takes me typically 30 minutes to
          connect to Internet, connect to Message Board, log on, and reply.

          One has to be strong to connect from South Africa !!

          Have a good one
          Dave Mac

          It's not so much what you don't know that gets you into trouble, but what you know for sure, that just ain't so. - Mark Twain.

          Comment


          • #6
            Re: Current Form or Another Form

            Question for Stan:

            If the variables are defined for the layout under the layout variables tab in the 'V' button - how do you refer to them in your button scripts? Do you have to use WITH local_variables() or do you just use 'dim myvar as c' in the script and A5 will use whatever default was set when the var was first defined? Or do you not dim them again at all?
            Robin

            Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

            Comment


            • #7
              Re: Current Form or Another Form

              I've never investigated and the documentation doesn't specify.
              There can be only one.

              Comment


              • #8
                Re: Current Form or Another Form

                Which is probably why I always add my layout variables to the session tab...then dim them as shared in my scripts. This thread got me thinking tho that if I have a 'searchfor' variable in two different forms that are both open, then the active form might get confused if the variable's value is not specifically reset.
                Robin

                Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

                Comment


                • #9
                  Re: Current Form or Another Form

                  When defining variables for a form there is a link Understanding Variable Scope which indicates that layout variables can only be seen by scripts and functions defined on the form. In the documentation regarding layout variables it says they cannot be defined via xbasic which should preclude being able to dim them.
                  There can be only one.

                  Comment


                  • #10
                    Re: Current Form or Another Form

                    easy way.
                    Variable for a form that needs to live after form is shut. dim global
                    Dave Mason
                    dave@aldadesktop.com
                    Skype is dave.mason46

                    Comment


                    • #11
                      Re: Current Form or Another Form

                      Originally posted by MoGrace View Post
                      Which is probably why I always add my layout variables to the session tab...then dim them as shared in my scripts. This thread got me thinking tho that if I have a 'searchfor' variable in two different forms that are both open, then the active form might get confused if the variable's value is not specifically reset.
                      You should write a function that does the search and an argument to the function that passes the value to search for from the layout variable that you already have.
                      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
                        Re: Current Form or Another Form

                        Originally posted by Stan Mathews View Post
                        When defining variables for a form there is a link Understanding Variable Scope which indicates that layout variables can only be seen by scripts and functions defined on the form. In the documentation regarding layout variables it says they cannot be defined via xbasic which should preclude being able to dim them.
                        So does that mean my layout scripts using those variables should be wrapped in WITH local_variables() / END WITH statements?
                        Robin

                        Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

                        Comment


                        • #13
                          Re: Current Form or Another Form

                          Originally posted by Al Buchholz View Post
                          You should write a function that does the search and an argument to the function that passes the value to search for from the layout variable that you already have.
                          What a great idea - have you got a simple example for me?
                          Robin

                          Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

                          Comment


                          • #14
                            Re: Current Form or Another Form

                            Originally posted by DaveM View Post
                            easy way.
                            Variable for a form that needs to live after form is shut. dim global
                            But Dave, this is about when you don't want variables that live outside the form ;)
                            Robin

                            Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

                            Comment


                            • #15
                              Re: Current Form or Another Form

                              destroy the variable when form is closed. OR used differnst variable names

                              as far as form, create forms on sets, not tables. duplicate the for? Make another identical set and use copy to.

                              just a couple ideas
                              Dave Mason
                              dave@aldadesktop.com
                              Skype is dave.mason46

                              Comment

                              Working...
                              X