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

re: indexing when open dbf

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

    re: indexing when open dbf

    i have one database with 2000 records in it every time i open it even when it is a child in a set it takes a minute or so to open i thin it its building the indexs my other databases don't seem to do that. is this normal or can i set it not to do it so it will open faster.

    thanks
    jerry

    #2
    re: indexing when open dbf

    You probably mean one table with 2000 records rather than one database (in Alpha terminology).

    The number of records is less meaningful to the index process than the physical (disk space) size. My theory is that the index process first builds a temporary file for the index and if succesful then it writes that file as the new index file. This would explain the time it takes to build.

    None of this explains why you are having the issue you see. Do you see the lapse if you look at the default browse or set for the table?
    If not, do you see the lapse if you view a form or browse with embedded filtering?
    There can be only one.

    Comment


      #3
      re: indexing when open dbf

      your right they change the names on me, (part time a5er).
      the table (dbf) is 367350 kb it took about 20 to 25 sec to open the default form and browse and the same to open a forms whether the dbf was parent or child. it actually seemed to open faster today than in past.

      thanks
      jerry

      Comment


        #4
        re: indexing when open dbf

        How many indexes do you have defined for the table? Are any of them built on complex (multi field combination) expressions? Can you zip and attach the table here if there is no sensitive data?
        There can be only one.

        Comment


          #5
          re: indexing when open dbf

          Check how your link is set up. If necessary, define an index for the child table to reflect the link. That, hopefully, should take care of your re-indexing issue.

          Tom

          Comment


            #6
            re: indexing when open dbf

            i packed the table and it still takes 20 sec to open the default form/browse and other forms.

            indexs
            name2+" " name1-" "mi

            pat_id

            signonfile(date0

            soundex(remspecial((name2-name1))

            Comment


              #7
              re: indexing when open dbf

              TRY REMOVING THE SOUNDEX INDEX

              I suspect the below indexes are typos, but just in case:

              name2+" " name1-" "mi
              NAME2+" "+NAME1+" " + MI
              pat_id

              signonfile(date0 ????


              soundex(remspecial((name2-name1))
              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


                #8
                re: indexing when open dbf

                delete soundex load time the same

                NAME_2-" "+NAME_1-" "+MI

                signonfile (is a date field)

                i'm begining to think it's not the index
                the table has 90 items and a number of field rules would that make it take longer to load

                Comment


                  #9
                  re: indexing when open dbf

                  no

                  try deleting all indexes and opening the default browse for the table

                  i don't understand that last index
                  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


                    #10
                    re: indexing when open dbf

                    the soundex index is to reduce the chance of entering a person into the dbf twice.

                    i deleted the indexs and opened the default browse and it took just as long then i opened the index list and they were all back their except for the soundex one

                    Comment


                      #11
                      re: indexing when open dbf

                      they were all back their except for the soundex one

                      Then field rules are adding the indexes to do some functionality that you have chosen.

                      Take a look at the field rules and/or it might be time for you to post a copy or email it to someone to get a another set of eyes on this.....
                      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


                        #12
                        re: indexing when open dbf

                        here is the dbf file which other ones do you need

                        Comment


                          #13
                          re: indexing when open dbf

                          the dbf file is 40 mb

                          Comment


                            #14
                            re: indexing when open dbf

                            Jerry

                            Your table has 410,697 records in it and they are all deleted.

                            I noticed that you have an operation that deletes all records. There are two ways to do that.

                            1. Use your operation to delete the records as you have been doing. The key to this is that the records are deleted in a logical sense but are physically still there. It then takes a table pack to physically remove the records.

                            2. Do a table erase which accomplishes the two parts of method 1. It does it by having exclusive control of the table and moving the end of file marker to the beginning of the table.

                            That's good for two reasons.
                            a. All the records are physically gone.
                            b. It's fast for tables of all sizes because it's doing the minimum amount of work to accomplish the task.

                            You are seeing a slow down in working with this table because of the baggage of the deleted records still being carried.

                            See attached image for additional help.
                            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

                            Working...
                            X