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

XBASIC - DELETING CHILD RECORDS

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

    XBASIC - DELETING CHILD RECORDS

    As a newcomer to xbasic - I am puzzled by the following:

    I have a Docket Header (parent table) with Docket Lines as child records. I have a DELETE button on a form, and I wish to delete all child records first before I delete the header.

    Example Docket Header has 3 child records A, B & C

    Can anyone please tell me why the following code displays and deletes the 1st & 3rd and leaves the 2nd one there ?
    -------------------------------------------------------
    dim mesg as c
    dim t1 as p
    dim t2 as p
    dim qty as n
    t1=table.current()
    t2=table.get("Docket Lines")
    t2.fetch_first()
    while .NOT. t2.fetch_eof()
    if t1.number = t2.number then
    qty=t2.Qty
    mesg=t2.stockcode+qty
    ui_msg_box("",mesg)
    t2.change_begin()
    t2.delete()
    t2.change_end(.T.)
    end if
    t2.fetch_next()
    end while
    -----------------------------------------------------

    yet if I take out the lines

    t2.change_begin()
    t2.delete()
    t2.change_end(.T.)

    all 3 records are correctly displayed in the message box.

    Am I not understanding how the delete works? It looks straight forward to me.

    Any help would be greatly appreciated.

    Many thanks
    Jenny


    #2
    RE: XBASIC - DELETING CHILD RECORDS

    If iI remember correctly,

    t2.delete() performs a fetch_next() as part of its process. Therefore your own .fetch_next() skips over the second child record.
    There can be only one.

    Comment


      #3
      RE: XBASIC - DELETING CHILD RECORDS

      Thanks Stan - but why does it only do that on the 2nd record? For example, I have tested 10 child records, and all are deleted except for the 2nd. Do you have any suggestions that may make this code work?

      regards
      Jenny

      Comment


        #4
        RE: XBASIC - DELETING CHILD RECORDS

        Check the docs explaining the delete method you're using. If the record pointer is being moved by Alpha Five itself, your fetch_next() moves it again. -- t

        Comment


          #5
          RE: XBASIC - DELETING CHILD RECORDS

          Hi Stan

          I have now changed the code to:

          dim mesg as c
          dim t1 as p
          dim t2 as p
          dim qty as n
          t1=table.current()
          t2=table.get("Docket Lines")
          t2.fetch_first()
          while .NOT. t2.fetch_eof()
          if t1.number = t2.number then
          qty=t2.Qty
          mesg=t2.stockcode+qty
          ui_msg_box("",mesg)
          t2.change_begin()
          t2.delete()
          t2.change_end(.T.)
          else //***** changed
          t2.fetch_next()
          end if //***** changed
          end while


          and this now appears to work ok, i.e. the fetch_next is NOT performed when the delete is done.

          Thanks for the help.

          regards
          Jenny

          Comment


            #6
            RE: XBASIC - DELETING CHILD RECORDS

            thanks Tom also

            Comment


              #7
              RE: XBASIC - DELETING CHILD RECORDS

              Jerry:
              In your set structure, did you choose cascade changes/delete?
              Gabe

              Comment


                #8
                RE: XBASIC - DELETING CHILD RECORDS

                Gabe

                No I haven't played with Referential Integrity yet. Will try that method as well.

                thanks
                Jenny

                Comment


                  #9
                  RE: XBASIC - DELETING CHILD RECORDS

                  Jerry:
                  You wrote: " I wish to delete all child records first before I delete the header. "
                  I am not quite sure what you are trying to do:
                  1-Are you trying to delete the child records then delete the parent record at the same time but in that sequence? or
                  2-Are you trying to delete the child records and preserve the parent record to delete in a later date?
                  Based on what you are trying to do, there could be VERY SIMPLE ways to do that without any need for any xbasic.
                  Please clarify.
                  Thank you
                  Gabe

                  Comment


                    #10
                    RE: XBASIC - DELETING CHILD RECORDS

                    Gabe

                    As I said initially, I am quite new at A5 so at this stage I am just playing with xbasic code to see how things work. I have just tried the Referential Integrity method with cascade changes/delete as you suggested - which excludes the need for xbasic code. That works fine when I want to delete parent and all child records.

                    I have the xbasic code working fine now too, so thanks everyone for your help.

                    regards
                    Jenny

                    Comment

                    Working...
                    X