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

Confued by Database Compact error message ...

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

    #16
    RE: Confued by Database Compact error message ...

    This is getting ridiculous!

    Now I have 3 tables that won't compact: progressnotes, patients, appointments.

    I need to know:

    what the heck is causing this

    and how to fix this

    Please help ....................

    Gary
    Gary S. Traub, Ph.D.

    Comment


      #17
      RE: Confued by Database Compact error message ...

      Here's an update:

      I created a new directory, copied all the files from the application directory to the new directory.

      Then, created New database with the same name as my app. Then added all tables and sets to the database. This copied added all tables, sets, layouts (forms, reports, etc) but no scripts in the code tab. I guess I'd have to copy ALL 250 of them one by one, but before I did that, I ran Database Compact, and the same errors occur.

      I guess this indicated that the adb was noty the culprit, but probably the individual data dictionaries for the errant tables. Am I correct?

      What would be the next step?

      Gary
      Gary S. Traub, Ph.D.

      Comment


        #18
        RE: Confued by Database Compact error message ...

        Okay, I seem to have resolved the problem. Here is what I did:

        As a matter of course, I make backups of my entire application at the end of every day. So, I went as far back as I needed to, to find a version of the app that caused no Database Compact errors.

        Once that was found, I copied my current data to that app. Ran Database Compact without any errors. Great!

        Then, I copied this working app to a safe directory, And then, added table data dictinaries of one module after another, one at a time, testing the Database Compact, aftrer adding each one. In this manner, I was able to get the app pretty much back to where it was most recently, and now have no more Database Compact errors.

        I am hoping that this problem is now over. It was not fun, to say the least. If it happens again, it will shake my confidence even further. I am left wondering what the heck caused that in the first place? Will it happen again? What will cause it? What can prevent it?

        Hope this experience can help others, and perhaps more importantly, lead to some discussion as to how to avoid this in the first place.

        Gary
        Gary S. Traub, Ph.D.

        Comment


          #19
          RE: Confued by Database Compact error message ...

          Gary,

          Did you try to comapct the troublesome tables one at a time only (not the entire adb)?

          Peter
          Peter
          AlphaBase Solutions, LLC

          [email protected]
          https://www.alphabasesolutions.com


          Comment


            #20
            RE: Confued by Database Compact error message ...

            Well ... it happened again ... and now to 2 tables: patients and progressnotes. I will attempt to fix it again, in the way I described above. But does anyone have any ideas as to why this is happening?

            Gary
            Gary S. Traub, Ph.D.

            Comment


              #21
              RE: Confued by Database Compact error message ...

              Peter,

              I must be dense, but I have not been able to get that script to work.

              Gary
              Gary S. Traub, Ph.D.

              Comment


                #22
                RE: Confued by Database Compact error message ...

                Can anyone tell me why this keeps happening?
                Gary S. Traub, Ph.D.

                Comment


                  #23
                  RE: Confued by Database Compact error message ...

                  No, other than something continues to corrupt your data dictionaries or some process is leaving a table open. Perhaps you could post the database with minimal data and have someone else give it a try. Have you tried a different computer?

                  Jerry

                  Comment


                    #24
                    RE: Confued by Database Compact error message ...

                    Jerry,

                    The application is huge.

                    I do not think any tables are open, as the problem still occurs after rebooting.

                    Also, the problem occurs on 3 different machines that I have tried.

                    I do think you are right that "something continues to corrupt your data dictionaries."

                    I do have a feeling it as something to do with running the application on a network, because I do not recall it ever happening when I run the application as standalone, or even during development. I run Database Compact often and do not get this problem until, I believe, the application is run on a network, and then at the end of the day, I copy the data files (dbf, cdx, fpt) from the server back to my laptop. Does that lead to any ideas? Perhaps it has something to do with locking issues?

                    Thanks for any other help with this.

                    Gary
                    Gary S. Traub, Ph.D.

                    Comment


                      #25
                      RE: Confued by Database Compact error message ...

                      Gary

                      If no design work is being performed, the data dictionaries shouldn't change. If the compact fails because a table is being left open, this might be harder to track.

                      There are many ways to try to isolate the problem. First, can you compact on the laptop, which I assume is off network? If / when it does, save all of the ddd, ddm, ddx, set, sem, sex, alm, alb, alx files to a backup. Save no data. Then when the compact fails after copying data, start restoring each file until the compact succeeds. That should isolate the problem file if the problem is in a data dictionary. Big IF.

                      If this has no effect, then the problem is a table being left open. The error should identify the table. Search for EVERY reference to this table anywhere in code. Verify that all dialog forms open and close correctly (if a process fails on a dialog form, the form may not close). Check every incidense where the table is opened and closed in code and verify that there is no way the table could be left open (bypassing a script line, ending a scripot before closing, etc) This might be quite a project.

                      Another possibility is locking issues from using referential integrity in a set. This will lock the child tables when the parent is placed in edit. While I don't think this could cause a problem, most developers suggest leaving integrity off.

                      There is a possibility that running on a network might have file locking issues, but I am not a network expert.

                      You say the database is huge. How huge is huge. You mighht be able to email it to someone else for testing if it is less than 5 meg, which is a typical limit for email. If it is larger, you can create multiple backup files to make each one smaller. This may be a viable alternative.

                      Jerry

                      Comment


                        #26
                        RE: Confued by Database Compact error message ...

                        If its a network locking issue, rebooting the server and the client machine should allow compacting. Is that the case??
                        Jerry said:"If no design work is being performed, the data dictionaries shouldn't change."
                        That is not exactly true. There is at least one end user function - word merge with templates - that write to the dictionaries. There may be others.
                        There are a number of things you can do in xbasic that write to the app dictionaries - adding dropping tables - shadow creates. Adhoc browses write to table dictionaries as well as app dictionaries. In theory when optimized you are only writing to your shadowed tables but maybe.

                        Comment


                          #27
                          RE: Confued by Database Compact error message ...

                          If its a network locking issue, rebooting the server and the client machine should allow compacting. Is that the case??
                          Jerry said:"If no design work is being performed, the data dictionaries shouldn't change."
                          That is not exactly true. There is at least one end user function - word merge with templates - that write to the dictionaries. There may be others.
                          There are a number of things you can do in xbasic that write to the app dictionaries - adding dropping tables - shadow creates. Adhoc browses write to table dictionaries as well as app dictionaries. In theory when optimized you are only writing to your shadowed tables but maybe.

                          Comment


                            #28
                            RE: Confued by Database Compact error message ...

                            If its a network locking issue, rebooting the server and the client machine should allow compacting. Is that the case??
                            Jerry said:"If no design work is being performed, the data dictionaries shouldn't change."
                            That is not exactly true. There is at least one end user function - word merge with templates - that write to the dictionaries. There may be others.
                            There are a number of things you can do in xbasic that write to the app dictionaries - adding dropping tables - shadow creates. Adhoc browses write to table dictionaries as well as app dictionaries. In theory when optimized you are only writing to your shadowed tables but maybe.

                            Comment


                              #29
                              RE: Confued by Database Compact error message ...

                              If its a network locking issue, rebooting the server and the client machine should allow compacting. Is that the case??
                              Jerry said:"If no design work is being performed, the data dictionaries shouldn't change."
                              That is not exactly true. There is at least one end user function - word merge with templates - that write to the dictionaries. There may be others.
                              There are a number of things you can do in xbasic that write to the app dictionaries - adding dropping tables - shadow creates. Adhoc browses write to table dictionaries as well as app dictionaries. In theory when optimized you are only writing to your shadowed tables but maybe.

                              Comment


                                #30
                                RE: Confued by Database Compact error message ...

                                If anyone resonds to this, you don't have to do it four times. Key was stuck - voila.

                                Comment

                                Working...
                                X