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

Closing a Form

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

    Closing a Form

    I have a form with an embeded brower in it. When I close the form it all ways saves the last record. I would like to be able to close it without saving, is there a way.

    Thanks,

    #2
    Re: Closing a Form

    Kerry,
    This is one of the automatic things that Alpha does (just like when navigating from row to row in a browse will save a record)....almost all times this is wanted I believe--you could add script to either the CanSave in the form or the OnRecordSave in field rules or add a cancel button that cancels pending changes in various ways......need to know more about it really to give a more specific response.
    Mike
    __________________________________________
    It is only when we forget all our learning that we begin to know.
    It's not what you look at that matters, it's what you see.
    Henry David Thoreau
    __________________________________________



    Comment


      #3
      Re: Closing a Form

      If you have a close button you can in design mode doubleclick and edit the close form/browse event. Click on edit and there is a check box If user has not saved the current record, save record before closing form. You could try this and see if it does what you want. If it does you could possible have two close buttons, one for save and one for don't save to cover both scenarios. Don't know reason for don't save, but I too have things that go contrary to accepted practices.

      Comment


        #4
        Re: Closing a Form

        Retract doubleclick, was in V10.5. In V9 it would be right click to access. Sorry for my error.

        Comment


          #5
          Re: Closing a Form

          Maybe just a little more information. what it does is if I have a blank record on the form and close it save the blank to the file. I would like it to ask if I would like to save so I can say no and it won't be saved, so I don't have blanks in the file.

          Comment


            #6
            Re: Closing a Form

            Kerry,
            Here is where the overwhelming part of Alpha comes in....there are several ways to prevent what you are having issues with and is as dependent on context as it is on how you personally want to do it!

            You could restrict entry for the form/browse and then if indeed you want to save a record, unrestrict...save...re-restrict. This can also be done utilizing the "read only" property instead.

            You could place code on the CanSave of the form/browse to say cancel a save if a certain field(s) are blank/incorrect.

            You could use field rules---the CanSaveRecord event perhaps.

            You could also make the user go to specific fields/etc and not let them out of it until they fill in the necessary data except maybe to use a Cancel button.

            You could also just have an operation performed whenever that will delete any records that are not filled in as you want....

            These are just the ones that occur to me now.....

            Choose one that you prefer....try it and if problems let us know!

            :)
            Mike
            __________________________________________
            It is only when we forget all our learning that we begin to know.
            It's not what you look at that matters, it's what you see.
            Henry David Thoreau
            __________________________________________



            Comment


              #7
              Re: Closing a Form

              Originally posted by MikeC View Post
              You could use field rules---the CanSaveRecord event perhaps.
              That would be my preference. That way it isn't necessary to worry about adding/editing the code in every form. Something like this - assuming the criteria is that you do not want to save the record unless either the first name, last name, or company name exists:
              Code:
              tc = table.current()
              IF tc.First_namf + tc.last_namef + tc.Comp_namef = ""
                  'All are blank - don't save the record.
                  cancel()
              END IF
              The only real issue is determining what criteria you want to use to determine whether or not to save the record.

              Comment

              Working...
              X