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

huge ALM file

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

  • huge ALM file

    My ALM file on an SQL based application is approaching 2GB. I only have four reports, what makes this file so large and can it be "compressed"?
    Steve Wood
    Join the ALPHA DEVELOPERS NETWORK
    There is no Cloud. It's just someone else's computer.
    Web - Mobile - Hosting - Products - Frameworks - Developer Resources
    AlphaToGo | IADN (100% Alpha Anywhere Websites)

  • #2
    Re: huge ALM file

    Steve, on the desktop side when an FPT file ( memo field ) grows that large it's a sign that the FPT is corrupted. I believe ( but don't know for certain ) that the ALM file is itself an FPT file. If correct this probably means the ALM is corrupted.

    Comment


    • #3
      Re: huge ALM file

      Many mods of the reports??.... probably just like the desktop side..

      A database compact should lessen the size...

      Unless it's corrupted...
      Was all of the available space on the drive used up? That would happen when a corrupted memo file stops growing short of 2 gb... it ran out of space...
      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: huge ALM file

        Yup, compact the database first off. This grows big fast and a database compact can bring it right back down.
        -Steve
        sigpic

        Comment


        • #5
          Re: huge ALM file

          You can always convert the library to a file system and then you don't have to worry about the ALM as there isn't one. All of items on the code tab, database properties, as well as all SQL reports and data sources are saved as files in a special library folder. The latest pre-release builds have greatly improved the process of using a file system and you can even publish the database library for SQL reports just as you can with the library.

          Comment


          • #6
            Re: huge ALM file

            Help,

            Just did as Jerry suggested and everything on the code tab has disappeared, my named connections don't work and my sql reports are gone. How do I get them back?

            Comment


            • #7
              Re: huge ALM file

              Lance - see the last few messages in this thread and my exchange with Selwyn:

              http://msgboard.alphasoftware.com/al...ht=file+system

              And note that Jerry's message is about improvements in the latest pre-release build.

              I think there's a lot of benefit here (I particularly like the longer function name capability). While I'm not using this right now I'd like to learn more about it and consider it -- some of this may simply be some adjustments in our own methods. I'm looking forward to the improvements Jerry notes, learning more about this and maybe learning how to make use of this feature.
              -Steve
              sigpic

              Comment


              • #8
                Re: huge ALM file

                Originally posted by Lance Gurd View Post
                Help,

                Just did as Jerry suggested and everything on the code tab has disappeared, my named connections don't work and my sql reports are gone. How do I get them back?
                You need the latest pre-release builds. The file system process in the last release build was flawed and did not work property for SQL reports, but did work for code on the code tab. When you set up a file system, just select the default path. What you need to find is where the <databaseName>.a5lib folder is located. It contains the file system files

                If you set up a file system before the pre-release builds, converting the file system back to a library WITH THE BUILD YOU USED TO CREATE the file system will work for code, but not SQL reports. If you converted to a file system previously, you may have to restore from a backup. If you don't have a backup, The file system conversion process creates backups of the original files as .old_alb, .old_alm, old_alx. Backup the database folder and rename those files as .alb, .alm, .alx. You will be back to a library system.

                If you created a file system with the latest pre-release build, you can still publish the database library for SQL reports in the publish process. The publish process converts the files system back to a temporary library and publishes the library, so the reports on the web work as they did before. The published folder will have an .alm file
                Last edited by JerryBrightbill; 05-12-2012, 07:48 AM.

                Comment


                • #9
                  Re: huge ALM file

                  I don't see an option to convert my file system backto a library on the code menu or the right click white space menu, looks like I will have to restore from my back up. Something I can't do until I go back to my office. There should have been a health warning on this.

                  Comment


                  • #10
                    Re: huge ALM file

                    I am using 2669 - 3921 and can't find anyway of restoring the library

                    Comment


                    • #11
                      Re: huge ALM file

                      Hi Lance,

                      Originally posted by Lance Gurd View Post
                      I am using 2669 - 3921 and can't find anyway of restoring the library
                      If you don't have backups, there is a chance the ALM file can be recovered if you don't overwrite the disk drive with new data. 1st step is to remove the drive so it can't be written to. Contact me by email (click on my name in the signature below) for details. Unfortunately, recovery can be somewhat expensive, which is why backup are essential.

                      Also, if you have an AEX compiled library version, I can recover most of the objects from it's ALM that created it, in most cases.
                      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


                      • #12
                        Re: huge ALM file

                        Originally posted by Lance Gurd View Post
                        I am using 2669 - 3921 and can't find anyway of restoring the library
                        As stated above, the file system conversion process creates backups of the original files as .old_alb, .old_alm, old_alx. Backup the database folder and rename those files as .alb, .alm, .alx. You will be back to a library system.

                        Comment


                        • #13
                          Re: huge ALM file

                          Hi Jerry, were changes made to how session variables work in this build? - I had all kinds of issues - had to retreat, it's a shame because there was a lot of good stuff in that build.
                          Insanity: doing the same thing over and over again and expecting different results.
                          Albert Einstein, (attributed)
                          US (German-born) physicist (1879 - 1955)

                          Comment


                          • #14
                            Re: huge ALM file

                            Hi Jerry, were changes made to how session variables work in this build?
                            Pete, I am interested in Jerry's answer, too. I have 3921 and have some other issues, too, but my session variables have suddenly become very unreliable. Unless they have a fix for this, I will also roll back because this is critical.
                            Carol King
                            Developer of Custom Homebuilders' Solutions (CHS)
                            http://www.CHSBuilderSoftware.com

                            Comment


                            • #15
                              Re: huge ALM file

                              Originally posted by peteconway View Post
                              Hi Jerry, were changes made to how session variables work in this build? - I had all kinds of issues - had to retreat, it's a shame because there was a lot of good stuff in that build.
                              As far as I know, there have been no changes to how session variables are handled. While the documentation for V11 states all session variables should be character springs, we haven't seen any issues with other datatypes.

                              We have not received any bug reports about session variables. If there is a specific problem we would like to hear about it.

                              Comment

                              Working...
                              X