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

cloning errors

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

    cloning errors

    has anyone had trouble with "cloning" records; i vaguely recall running into this once before, a while back. the clone is not always writing all the field values to the new record - but when I change it to the blob/data_set routine, it works perfectly, time after time.

    since I've run into this, now, at least twice, for the time being I'm going to abandon the clone approach infavor of the data_set
    Cole Custom Programming - Terrell, Texas
    972 524 8714
    [email protected]

    ____________________
    "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

    #2
    RE: cloning errors

    Martin, I'm curious. What 'cloning' method are you referring to?

    -- tom

    Comment


      #3
      RE: cloning errors

      Tom,

      Perhaps it's the Dolly (the Sheep) method? {:?)

      Ira
      Regards,

      Ira J. Perlow
      Computer Systems Design


      CSDA A5 Products
      New - Free CSDA DiagInfo - v1.39, 30 Apr 2013
      CSDA Barcode Functions

      CSDA Code Utility
      CSDA Screen Capture


      Comment


        #4
        RE: cloning errors

        Tom & Ira
        Cole Custom Programming - Terrell, Texas
        972 524 8714
        [email protected]

        ____________________
        "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

        Comment


          #5
          RE: cloning errors

          Martin:

          Take a look at this thread:
          Duplicate code fails in 4.5.266
          which is about 4 pages back on the board.

          If you are at 4.5.266 it may be the same issue as the code is similar.

          Cian has a demo of the problem which appears in 4.5 but not in 4.03 and 5.x beta.

          I also have a workaround thanks to the kindness of Peter Wayne (and Jerry Brightbill and others) to which you are welcome.

          Cian is on vacation so for the moment I am in wait mode. However if you are concerned with only the posted example you are welcome to the workaround. It uses two sets of pointers.

          Bill
          Bill Hanigsberg

          Comment


            #6
            RE: cloning errors

            Bill - I would be very interested in the workaround, as I am very locked into 466, with the new browse commands

            PS: VACATION!! real programmers don't go on vacation!
            Cole Custom Programming - Terrell, Texas
            972 524 8714
            [email protected]

            ____________________
            "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

            Comment


              #7
              RE: cloning errors

              Hi Martin,

              Check your email.

              Bill
              Bill Hanigsberg

              Comment


                #8
                RE: cloning errors

                Martin,

                Check your email again.

                Bill

                note to others: we have a weird anomaly of some kind.
                Bill Hanigsberg

                Comment


                  #9
                  RE: cloning errors

                  Martin,
                  I have used record_clone() in a similar way to your example without a problem. But, I did learn the hard way that the two tables must be absolutely, positively, exactly the same. Same field names, definitions and order. The best way to ensure this is to duplicate the first table to the second table. Different field rules don't seem to be a problem (althought mine are the same for both tables), just the structure.

                  Jerry

                  Comment


                    #10
                    RE: cloning errors

                    Hi Jerry,

                    If I interpret you correctly, you don't think Martin's problem bears any relation to the problems with the duplicate code we discussed in the earlier thread, right?

                    Bill
                    Bill Hanigsberg

                    Comment


                      #11
                      RE: cloning errors

                      yes - both files are identical except in name and field rules. My archive files have no rules at all.

                      one reason I think its the language is that if I try it over and over, it will only fail occasionally - testing with the same records.

                      what worries me, though, is that my fix has been to use the data_set routine instead of the clone routine, and that is the one Bill was having trouble with!
                      Cole Custom Programming - Terrell, Texas
                      972 524 8714
                      [email protected]

                      ____________________
                      "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

                      Comment


                        #12
                        RE: cloning errors

                        Martin,

                        I don't think the problem is the method: data_set. The problem (in 4.5 only) appears to be using the same pointers to get and set the data.

                        Treat the above as a hyothesis only. Still, consider that the workaround which runs fine also uses data_set. This is why I suspect something else is at the root of the problem.

                        Bill
                        Bill Hanigsberg

                        Comment


                          #13
                          RE: cloning errors

                          Bill,
                          I use cloning to copy only one record during an operation, not a sequence or an array. I wonder if cloning multiple records results in a timing problem where the first clone is still being created as a script tries to create another. If the A5 clone process locks the table or record during the process, this could cause a problem. In most cases where I need to copy multiple records, I create a loop where I copy each field value into an array, then enter a new record and copy the array values into the new record. In this way, I know that each record is saved and complete before the next new record is created. Cloning is much easier.

                          Jerry

                          Comment

                          Working...
                          X