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

Prevent row delete in emb browse

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

    Prevent row delete in emb browse

    I want to prevent user from deleting a row in an emb browse if a condition is true (calc field > Max amount). In Field Rule I can see there is a CandeleteRecord event. However, I couldn't find a similar event for embedded browse.

    #2
    Re: Prevent row delete in emb browse

    Gaby,
    what mechanism are you providing for the user to delete an embedded browse record (row)? A button? The browse OnRowDblClick? Could you not script this as an if-then statement within the mechanism that you have for the user to delete the record?
    Mike W
    __________________________
    "I rebel in at least small things to express to the world that I have not completely surrendered"

    Comment


      #3
      Re: Prevent row delete in emb browse

      Hello Mike:
      Just native mechanisms: Ctrl-D or right click + Delete or from the menu Records -> Delete.

      Comment


        #4
        Re: Prevent row delete in emb browse

        Gaby, whether the field rule record event will work depends upon where the calc field and the Max_Amount fields exist. Are they fields in the same table displayed in the browse? Are they fields in other tables? Is the calc a simple calc display field existing only in the form layout?

        Comment


          #5
          Re: Prevent row delete in emb browse

          Hi Tom:
          The calc field and max amount are layout based, more precisely: I have a parent-child-G.child. I want to prevent deletion of record/row in 1st emb browse (child table) if sum of a field in 2nd emb browse (G. child table ) exceeds say $100 (the sum is layout based calc field).

          Comment


            #6
            Re: Prevent row delete in emb browse

            Hi Gaby,

            I'd try writing a script in the CanDeleteRecord event in Field rules. The script would determine if your form is open. If so it would check object values in the layout to determine whether to "cancel" the delete or not.

            If the script can't "see" the form it won't be able to pull object values from the layout. In this case you might use tablesum() to compute the sum of the desired grandchild records and then determine if the delete should be cancelled or not.

            Later on ...

            Yes, the first approach will work fine. Here's an example using the Invoice_items table in Alpha Sports to read text from an object in the Invoice form.

            Code:
            if is_object(":Invoice") then 
            	pointer = obj(":Invoice")  'get pointer to the open form
            	msgbox("","Sales rep is " + pointer:Sales_rep.text) 'retrieve object text and display it
            	cancel()
            else
            	cancel()
            end if
            Last edited by Tom Cone Jr; 02-10-2009, 12:01 PM. Reason: Confirm approach

            Comment


              #7
              Re: Prevent row delete in emb browse

              Since you can test on your value... what about this.

              On the OnArrive and OnRowChange of Browse2

              If :frmname:browse1:fieldname.value > 100 then
              :frmname:browse2.restrict_delete = .t.
              Else
              :frmName:browse2.restrict_delete = .f.
              end if

              Restrict the deletion of records for the whole browse of the grandchild records if their parent tests true for your value.

              Does that make sense?

              David

              Comment


                #8
                Re: Prevent row delete in emb browse

                Hi Tom:
                Thank you for take the time. this will get me started.

                I tried many times to use Events in FR but when using action scripting to create a script like (cancel script) I keep having the followinmg problems:
                1) When I open the expression builder in a script (expl in cancel script) pressing F2 to display Tables & Fields always produces an error message saying "A5 cannot display field names because there is no table open"
                2) When I create the script with its expression outside the FR (like in from events) and paste it in the Expression builder in FR, it always returns <invalid expression>; the same script works perfectly with Form events.

                Hi David:
                the .restrict_delete sounds great; was not aware a such function. I'll experiment with it. Thanks David.

                Comment


                  #9
                  Re: Prevent row delete in emb browse

                  What I'm finding really helpful is... when in the code editor, I click on the Task List on the Menu bar and turn on the XBasic Explorer. I just pile through the list of methods and properties available for an object until I find something useful. I'm finding that A5 will almost always have something that will do for a task. Just not Bitmap1.rotate.... rats!

                  Comment

                  Working...
                  X