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
Devcon 2020 Goes Virtual! LEARN MORE >

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

Delete Record goes through onsave

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Delete Record goes through onsave

    Does anyone know why delete record (in a modal form) fires the onsave record event (field rules/events/record events/onsave record) after a record is deleted?

    Regards,
    Scott
    Tags: None
    #2
    RE: Delete Record goes through onsave

    Yes.

    In Alpha Five deleting a record does not remove it from the table, it marks it for deletion. Saving the "mark" to the record is required to do this. -- t

    Comment

      #3
      RE: Delete Record goes through onsave

      Thnaks Tom - gota love the quirky bits...

      So in onsave record event code, one should always test if a record is really being saved - or if it is being deleted/save.. what test do you recommend for this?

      Regards,
      Scott

      Comment

        #4
        RE: Delete Record goes through onsave

        ""gota love the quirky bits... ""

        DBF files have worked this way since before the IBM PC was invented.

        -- t

        Comment

          #5
          RE: Delete Record goes through onsave

          ""So in onsave record event code, one should always test if a record is really being saved - or if it is being deleted/save.. what test do you recommend for this? ""

          I'm not sure. I tend to use form level event code for this kind of thing. Data entry in my apps is permitted only through specific forms which I control tightly (or at least try to!). Deletes aren't permitted unless they push the right button. The OnPush event script for that button knows that a delete is happening so I handle any necessary post delete processing there.

          Your question suggests you don't fully grasp my previous. The OnSaveRecord event is firing because the record is being saved not because it's being 'deleted'. When the record is marked for deletion its "really being saved", to use your words.

          One approach I'd investigate if I needed a field rule solution would be to try to determine whether the record pointer moves when the OnSave fires. If it hasn't moved you could use something like tbl.current().is_deleted() to determine if the "current" record is marked for deletion.

          Let us know what you find out.

          -- t

          Comment

            #6
            RE: Delete Record goes through onsave

            Testing this_tbl.is_deleted() for True/False seems to be the best way to go.

            I guess it is just one of those traps - if you don't know that a Delete command at the form level will fire up any onsave record event code then you can get caught.

            Regards,
            Scott

            Comment

              #7
              RE: Delete Record goes through onsave

              I think maybe you want the a_deleting_record variable. The help file has more details but you have to know the variable name to search for it. Or, now that I've found it, look under Field Rule Record Events.

              This is why I still like my own A5v5 help file. I found the variable name very quickly by searching for Delete. Keywords ONLY relate to the function rather than anything found in the text or examples. So, looking up Delete didn't have 308 hits like the A5 files do. (Not blaming Ed here. See the next sentence.) However, setting up those keywords was a lot of work. Since nobody ever purchased it, it's now free even though the web page hasn't been updated to say that yet. It doesn't provide more info (actually there is less but it should have all A5v5 and many A5v6 xbasic commands in it) but it often comes in handy for finding a command when you don't know or remember the command name. I add v6 commands whenever I find one that may be hard to find in the A5 help file.

              Cal Locklin
              www.aimsdc.net

              Comment

                #8
                RE: Delete Record goes through onsave

                Thanks, Cal. That's a useful system variable to remember.

                -- t

                Comment

                  #9
                  RE: Delete Record goes through onsave

                  That's a good option - thanks Cal. I will also take a look at your help file.

                  Regards,
                  Scott

                  Comment

                    #10
                    RE: Delete Record goes through onsave

                    Cal,

                    I use your V4 help almost daily. I now downloaded your V5 help. It looks GREAT. I expect it will make my migration to V6 much easier.

                    Thank you very much

                    Tom

                    PS the $15 you are asking is a steal.

                    Comment

                    Previous template Next
                    Working...
                    X