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

is the Function 'close_if_exists()' still exist

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

  • is the Function 'close_if_exists()' still exist

    Hi There,

    When trying to run Function 'close_if_exists()' 'Function is not recognized' is displayed.

    Has this been deleted from available Functions ?

    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: is the Function 'close_if_exists()' still exist

    I believe that was a udf defined in AlphaSports. You can of course copy it from there and save it in your database.

    Or, as Selwyn answered a similar question.

    dim window_to_close as c
    window_to_close = "customers"
    dim tempObj as p
    tempObj = obj(window_to_close)
    if is_object(tempObj) then
    tempObj.close()
    end if
    Last edited by Stan Mathews; 09-09-2016, 08:20 AM.
    There can be only one.

    Comment


    • #3
      Re: is the Function 'close_if_exists()' still exist

      Originally posted by Stan Mathews View Post
      I believe that was a udf defined in AlphaSports. You can of course copy it from there and save it in your database.

      Or, as Selwyn answered a similar question.

      dim window_to_close as c
      window_to_close = "customers"
      dim tempObj as p
      tempObj = obj(window_to_close)
      if is_object(tempObj) then
      tempObj.close()
      end if

      Hi Stan,

      Thanks for your response. I'll dig it out and give it a try.

      (the above from Selwyn, seems to suggest that the code actually closes the "customers'.

      I actuallw want to check that "Customers" is closed. Are we on the same page ?)

      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: is the Function 'close_if_exists()' still exist

        In the sample posted

        is_object(tempObj)

        returns true if customers is open, false if it isn't.
        There can be only one.

        Comment


        • #5
          Re: is the Function 'close_if_exists()' still exist

          Originally posted by Stan Mathews View Post
          In the sample posted

          is_object(tempObj)

          returns true if customers is open, false if it isn't.

          Hi Stan,

          Thanks for your input. I have a real problem which I am not sure
          whether sensing Form closing, is going to help. Just casting around.
          Maybe you can spot where I need to fix.

          I have attached a few Screen dumps


          19 Sep 2016

          Problem with closing Form and reopening a different Form.

          Sequence as follows

          'Debt_Xact_Crn_m' Form.jpeg

          'Debt_Xact_Crn_m' Form Editor.jpeg

          'Debt_Xact_Xxx_m' Action Closing Form.jpeg

          'Debt_Xact_Xxx_m' Action 'Opening Next_Acc_m' Form.jpeg

          'Next_Debt_CrNote_Acc_m' display correctly.jpeg

          'Next_Debt_CrNote_Acc_m' display before closing 'Debt_Xact_Crn_m' - hang.JPG

          My problems starts with 'Debt_Xact_Crn_m' Form.jpeg on pushing btn_Commit_Transaction (F9).

          Refer 'Debt_Xact_Xxx_m' Action Closing Form.jpeg I have this Action closing the Form.
          This XBasic Action has been Converted to XBasic to allow different Forms to be closed
          dependent upon data retrieved from Table 'Params_tnm'. Refer 'Params_tnm,jpeg.JPG'

          Some processing is then done Conditions dependent.

          Refer 'Debt_Xact_Xxx_m' Action 'Opening Next_Acc_m' Form.jpeg'
          This Action has been converted to XBasic to allow different Forms to be opened.

          Now logic seems to give up and luck takes over !
          If we are lucky then 'Next_Debt_CrNote_Acc_m' display correctly.jpeg' displays (95% of cases)

          If however, we are unlucky then
          'Next_Debt_CrNote_Acc_m' display before closing 'Debt_Xact_Crn_m'.JPG' display (5% of cases)
          In this case the Title? Bar display that it is displaying 'Next_Debt_CrNote_Acc_m'
          with its Find by Key box correctly prompting, while the 'Debt_Xact_Crn_m' Form.jpeg has not obeyed the
          Close Form Action ? Only intermittently !

          I have tried many and varied differently stratergies to shake this one, to no avail.

          I am hoping that you cas spot the problem area with your extensive exposure to Alpha5.

          if not I can try and sqeeze my App down to the required size to send you my coding.
          However, this is a real mission, which I am hoping we can circumvent.

          PS. I see I can only add 5 attachments.
          Will seend the other 3 seperately
          Attached Files
          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: is the Function 'close_if_exists()' still exist

            Hi Stan,

            Here are the other Attachments
            Attached Files
            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


            • #7
              Re: is the Function 'close_if_exists()' still exist

              I would think it a timing issue. The easiest way to avoid such is

              codeTxt = <<%code%
              form.open()'appropriate command here to open next form
              %code%
              'command here to close the current form
              parentform.close() '??
              on_xbasic_idle(codeTxt,"R")
              There can be only one.

              Comment


              • #8
                Re: is the Function 'close_if_exists()' still exist

                Originally posted by Stan Mathews View Post
                I would think it a timing issue. The easiest way to avoid such is

                codeTxt = <<%code%
                form.open()'appropriate command here to open next form
                %code%
                'command here to close the current form
                parentform.close() '??
                on_xbasic_idle(codeTxt,"R")
                Thanks for the input Stan.

                I'll let you know if my luck changes
                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

                Working...
                X