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

"CLOSE" button on dialog

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

    "CLOSE" button on dialog

    I have a form that I pop-up as a dialog (form.view("name",dialog)) that works just fine. However, to close the form, the user has to click on the X.

    I would like to put a button on it to close it, which would also prompt the user to save changes. How can I do this?

    As always, any help is greatly appreciated.

    #2
    RE:

    Bill, go ahead and put a Close button or Confirm button on the Dialog Form. Don't forget though that Close button only "hides" the form, it must be closed when you return to the calling script.

    Open dialog form
    go out to dialog form - "close" it
    return to calling form
    close the dialog form.

    -Barry

    Comment


      #3
      RE:

      I have exactly this set up. I just converted my action script to xbasic (and eliminated the error trapping...)
      NOTE: this script does NOT close the form as it is on the dialog form. You need to close the form using the script that opened it.

      select
      case parent.mode_get()="ENTER"
      ax_response = ui_msg_box("","Save Record ?", 4)
      if ax_response=6 then
      ax_choice="YES"
      else
      ax_choice="NO"
      end if
      select
      case alltrim(upper("Yes"))==alltrim(upper(ax_choice))
      parent.commit()
      case alltrim(upper("No"))==alltrim(upper(ax_choice))
      end select
      end select
      parent.close()

      END

      Comment


        #4
        RE:

        Bill, your Open button would look like this
        {{below is a sample from one of my files}}

        :form.view("glcodes","dialog")
        :glcodes.close()
        parentform.resynch()

        then on your dialog box place a button to exit.
        select the Built in action
        then Form/Browse Operation, then
        Close the current form
        you will get an inline xbasic code that looks like the
        following:

        dim mode as c
        mode = parentform.mode_get()
        if mode = "ENTER" .or. mode = "CHANGE" then
        parentform.commit()
        if parentform.mode_get()"VIEW" then
        ui_msg_box("Unable to save your changes","Please correct and save, or discard your changes", UI_STOP_SYMBOL)
        end if
        end if
        parentform.close()

        this will take you back to the form that called the dialog box.

        Jerry

        Comment


          #5
          RE:

          Many thanks to all that responded.

          Comment

          Working...
          X