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

Delete of record in embedded layout

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

    Delete of record in embedded layout

    I can't get Action Scripting to delete a record in an embedded layout.

    I bring up a form based on a set and using a key to match an assembly with parts in an assembly. This form is supposed to allow the addition of parts to an assembly and removal of parts from the assembly. This addition works great. The button that is supposed to delete the part selected in an embedded browse doesn't do anything.

    If someone could either correct what I'm doing in action scripting, or give me an alternative in Xbasic, I'd be very happy.

    I've attached a subset of the application. To get to the form with the problem, bring up "Plant Menu" and select "Create Assembly". The button having a problem is "Remove Part".

    Edit: The attachment was too large, making it smaller.
    Last edited by Tony Saladino; 10-05-2005, 04:11 PM. Reason: Attachment 2 large

    #2
    Tony,

    Place a button on the Form and on the OnPush event in Action Scripting:
    1. Select Delete Record
    2. Current Form or Browse
    3. Select the Embedded Browse radial button
    4. Enter the Browse Number that is holding the records that can be deleted.
    5. Save, Save the form.

    In the form select the record in the browse to be collected and click the button, should work!

    Alan

    Comment


      #3
      Alan,

      That's exactly what I did. Which is why I'm now posting to the message board. ;)

      Now, if my zip file wasn't 67 KB too big, I'd be able to demonstrate that. I'm currently trying to figure out why the DDM file for my single menu is 4.5M pre-zipped.

      Tony

      Comment


        #4
        Just needed to pack the tables for the DDM file to make the zip file smaller. Here's the attachment.
        Last edited by Tony Saladino; 10-05-2005, 05:04 PM. Reason: To avoid confusion

        Comment


          #5
          Browse1 is marked read-only and thus records cannot be deleted.

          If you mark it disabled and not read-only you may get the behavior you want.
          Last edited by Stan Mathews; 10-05-2005, 05:15 PM.
          There can be only one.

          Comment


            #6
            I have an partial answer to my problem.

            I had the embedded browse as "Read Only" so the user would be forced to use the buttons instead of going into the browse. When I removed "Read Only" from the browse, the action scripting worked.

            So, I added "Allow Edits" before the deletion and "Disallow Edits" after the deletion. With the embedded browse set to "Read Only" the deletion still does not occur.

            I would really like this to work with the embedded browse set to "Read Only"

            Comment


              #7
              I amended my original post with a suggestion.
              There can be only one.

              Comment


                #8
                Thank you Stan,

                That works nicely. I just need to remove the "New Record" line to make it look nice. I believe I saw a way to do that, so I should be fine now.

                Thanks again,
                Tony

                Comment


                  #9
                  This didn't work as nicely as I thought. The user needs to select the part to be removed before clicking the "Remove Part" button. With the browse disabled, this is impossible.

                  I think it's time for me to look at Xbasic for a solution. Time to do some manual coding. :)

                  Comment


                    #10
                    Tony,
                    I have done something similar by leaving the browse readable (read only unchecked) and setting the individual columns in the browse to read only.
                    Tim Kiebert
                    Eagle Creek Citrus
                    A complex system that does not work is invariably found to have evolved from a simpler system that worked just fine.

                    Comment


                      #11
                      Tony,

                      Do not disable the browse object. You can leave it read only and then do the following in action scripting:

                      1 - Set the browse property "Read Only" to .f. using the Object properties(set and get) action and select Set properties of object(s)

                      2 - Delete your record in the browse.

                      3 - Set the browse property "Read Only" to .t. using the Object properties(set and get) action and select Set properties of object(s)

                      Scott

                      Comment


                        #12
                        Scott,

                        I've got number one and number two working. If I do number 3 immediately it won't allow the edit to occur. I need to wait on dialog response, the Ok for deletion of record, before I allow the deletion to occur.

                        I don't know how to set a conditional waiting on a standard dialog. I'm going to start perusing the documents.


                        Tim,

                        Although your method works well, it leaves the pull down menus with the capability of deleting a record.

                        Tony

                        Comment


                          #13
                          Tony,

                          Sorry, I don't use action scripting so I might have over looked a step. Between step 2 and 3 of my post try adding the following action:

                          Xbasic->Wait for Idle

                          Scott

                          Comment


                            #14
                            Hi Scott,

                            No problem. We have a winner. Thank you very much.

                            Tony

                            Comment


                              #15
                              Doh! So it does. I tried Stan's idea, which I thought was better than mine anyway, and got the same behaviour as you. I put an xbasic - Wait for Idle after the delete record steps and it now works.
                              Tim Kiebert
                              Eagle Creek Citrus
                              A complex system that does not work is invariably found to have evolved from a simpler system that worked just fine.

                              Comment

                              Working...
                              X