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

Update problem with a set

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

    Update problem with a set

    I have tried this several ways.

    I have a set with several child tables. the ones I am concerned with are connected by ACCT. ACCT is an auto-incremented field in names.dbf.

    I wished to change the field to coincide with recno(). Recno() is a numeric field so the code as shown below to change it to character.

    I did my do-dillegence and made a new set with only the tables needed that are connected by acct, made the connection to refferentil integrity cascade. Removed the autoincrement in names.dbf-acct.

    When i run the update(pictured below), it runs for about 20 minutes and then gives an error of File Locking exceeds 512.

    It does update most of the records.

    All help appreciated

    Dave
    Dave Mason
    [email protected]
    Skype is dave.mason46
    Tags: None
    #2
    Re: Update problem with a set

    Forgot the picture:
    Dave Mason
    [email protected]
    Skype is dave.mason46

    Comment

      #3
      Re: Update problem with a set

      Originally posted by DaveM View Post
      then gives an error of File Locking exceeds 512.

      Dave
      That's a referential integrity limit. You must have a parent with more than 512 children.

      To avoid, you'll need to remove the referential integrity and update each of the tables separately.

      It'll usually involve another field to hold the new linkage value until all of the tables are updated..
      Al Buchholz
      Bookwood Systems, LTD
      Weekly QReportBuilder Webinars Thursday 1 pm CST

      Occam's Razor - KISS
      Normalize till it hurts - De-normalize till it works.
      Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
      When we triage a problem it is much easier to read sample systems than to read a mind.
      "Make it as simple as possible, but not simpler."
      Albert Einstein

      http://www.iadn.com/images/media/iadn_member.png

      Comment

        #4
        Re: Update problem with a set

        I do not have a table with 512 of any kind of entries and certainly not 52 children. I did find an entry in the master table that is all screwed up. Not sure of all it's problems yet, but working on it. My entries never have more than 18 children of any kind, fortunately.

        Thanks for the input. The bad record may be worse than I think though.

        Fortunately I am working with a copy right now.

        Dave
        Dave Mason
        [email protected]
        Skype is dave.mason46

        Comment

          #5
          Re: Update problem with a set

          Dave:
          You are asking for trouble:
          Let's say you have a parent with ACT 5
          once you update it, the new linking field now would have the recno+10 which might end up being, say 112
          What you are forgetting is the fact that, somewhere in that very same table, you have a parent with that same value of 112. Now and until that record is updated, the one that was updated from 5 to 112 will have it's children plus the children of the one that have 112 from the start. Are you still with me? this is a mess, because when alpha gets around to 112, now it has it's original children plus the newly added ones! and before you know it alpha is working through stacks and stacks of unrelated children that were wrongly attached to the wrong parent.

          The easy way is to add another field in the parent, update it separately, then update the children accordingly then remove the original ACT field.

          Comment

            #6
            Re: Update problem with a set

            Gabe,

            Most of it went super good. I had a bad record. You are "very" right in theory and I have not gotten that far. I think I will take your advice and change procedures on fresh(copied) data. I can change the whole thing to a much higher number such as add 5000 to what I have first or concatenate in my instance with jjj or something before I do the actual change to recno(). Most of my records are totally different anyhow and would not be affected.

            I do know to do it all in a set at one time so the problems are not too extreme.

            dave
            Dave Mason
            [email protected]
            Skype is dave.mason46

            Comment

              #7
              Re: Update problem with a set

              All,

              For the first time, I ran into this problem today. Of course I made sure everything was updated, etc. The application I am running has over ten thousand records in 9 separate databases linked together in a set. The only tip-off I got was that I got the File Locking Error 512 9 times! When I looked more closely at the set (after trying a hundred other things) I found that I had turned on referential integrity for all 9 dbf's.

              I'm posting this so someone else doesn't have the same problem.

              BTW, what's the point of having referential integrity if it's not to be used? In theory, it should work properly.

              Charlie

              Comment

                #8
                Re: Update problem with a set

                Originally posted by Charles Hoens View Post
                BTW, what's the point of having referential integrity if it's not to be used? In theory, it should work properly.

                Charlie
                Just because it can't be used everywhere, doesn't mean that it can't be used in some places.......

                But it sure is nice to where and when it shouldn't be used... and I think you found one.... :)
                Al Buchholz
                Bookwood Systems, LTD
                Weekly QReportBuilder Webinars Thursday 1 pm CST

                Occam's Razor - KISS
                Normalize till it hurts - De-normalize till it works.
                Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
                When we triage a problem it is much easier to read sample systems than to read a mind.
                "Make it as simple as possible, but not simpler."
                Albert Einstein

                http://www.iadn.com/images/media/iadn_member.png

                Comment

                  #9
                  Re: Update problem with a set

                  BTW, what's the point of having referential integrity if it's not to be used? In theory, it should work properly.
                  I don't think that you can't use it, the issue here is you have way too many tables in the set, that would have been less of a problem if you didn't have ref integrity turned on, but with it turned on, alpha will try to lock all records in all these tables and that's where the problem comes from.

                  If you in the mood for testing, take one table out at a time and see at what point the error will go away, that would be your hint of how many alpha could handle at a time. That figure is usually around 6, though that is pushing it.
                  Last edited by G Gabriel; 07-01-2008, 07:47 PM.

                  Comment

                    #10
                    Re: Update problem with a set

                    Thanks guys. It's worked flawlessly for years this way with thousands of records in place, that's why it was hard to find the error. One thing though that I learned from my old mainframe programming days was to set up and maintain a log file. When this routine ran, it was the log file that helped to point me in the right direction.

                    Charlie

                    Comment

                    Previous template Next
                    Working...
                    X