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

Buggy Report Writer

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

    #16
    RE: Buggy Report Writer

    I use an old slow machine as well as very fast ones. I rarely have a problem. I also have very little elsy running while doing reports and forms. Not even a screen saver.

    I have experienced some slow downs though.

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

    Comment


      #17
      RE: Buggy Report Writer

      I can too report that when designing forms/reports that the design screen begins to behave "funny" after in design mode for some time. When I notice I typically save the form/report, shutdown A5, and then restart. Things again work fine for a while, then it seems like it starts to happen again. Repeat the process and it goes away, only to come back after time. It used to be that I'd only notice the menus would not repaint. Now I also am beginning to notice that when I click on a field object and try moving it with the arrow or dudge with shift-arrow, nothing happens. Save, close A5, and reopen A5 - and they work for a while. Using Win98SE, PIII 800 MHZ. Seems to be same issue at home on WinME PC.

      Mike
      Thank you,
      Mike Konoff

      Comment


        #18
        RE: Buggy Report Writer

        I don't think it the OS - its the editor. My advice is to immediately close and reopen at the first sign on "wierdness." Otherwise you can lose a big chunck of the report.
        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


          #19
          RE: Buggy Report Writer

          I would think since so many people are having issues that maybe alpha software would reinvestigate. It really cuts into my work time I know, I don't know about anyone else.

          Brandi

          Comment


            #20
            RE: Buggy Report Writer

            Brandi,

            What's needed is a repeatable sequence. Step by Step. Mouse click by mouse click. Leading to a crash or 'odd' behavior. Until someone can produce this it's unlikely (in my opinion) that Alpha will spend time on it.

            -- tom

            Comment


              #21
              RE: Buggy Report Writer

              I wish I had the time to volunteer for that position, but I am here complaining about how this is a time absorber...so unfortunately I don't (maybe if they paid my salary, I could search down their bugs, you know :-) but the big bosses, my clients want to know why I can't deliver this report).

              It seems to me, if they see several people having the same issue, they just might take a look. It kinda goes back to what I said before which was that there isn't a certain combination of key strokes or events that occur, it is random and looks to me to be similar to a memory leak. But I don't think I am going to get a resolution here. Thanks to everyone for your input, I appreciate you taking your time.

              If anyone thinks a new thread with a poll of how many are having issues would be a good thing, let me know, and I will start one.

              Thanks,

              Brandi

              Comment


                #22
                RE: Buggy Report Writer

                Tom,

                I do not think it is the kind of thing that you can or even need to say, "It's x,y, then z and bang h happens." The problems I have don't follow any kind of pattern like that and they can usually be cleared by exiting the report design and then coming raight back in. It seems like a resource issue of some sort, but it quite simply is not a matter of my high powered machine not being high powered enough.

                My most frequent issue is that after a bit of editing one cannot move an object with the arrow keys, which is sometimes (especially Shift+arrow) far superior to dragging with the mouse. For me the problems are just irritations, not show stoppers, and Alpha isn't much interested in fixing mere irritations, at least not in v5, or at least not right now.

                Ray Lyons

                Comment


                  #23
                  RE: Buggy Report Writer

                  Ray

                  I think you framed the issue very well as a resource issue and more of an irritant than a real defect. I have similar problems with a number of programs and a some are much worse than Alpha, which leads me to believe that Windows, even in the latest versions, doesn't always handle resources as well as it should. Win98 and WinME were particularly problematic and when I used them continuously in a work computer, I had to reboot at least once a day to clear memory issues.

                  I do a lot of graphics work and suspect many problems are related to video problems as much as anything. Different computers with different video cards show significant differences in behavior. I found, as have others, the best solution in all Windows programs is save your work frequently, close and reopen programs periodically, and keep backups. In A5, I also get out of layout editors from time to time and compact quite often. I had some problems in the past, but not since I started using that approach and moved to Win2000 and WinXP.

                  I don't consider this an Alpha issue, but more of the consequence of pushing a system to the limits. When I see how many different files are open in a typical functioning system, I am surprised we don't see more clashes.

                  Jerry

                  Comment


                    #24
                    RE: Buggy Report Writer

                    Brandi,

                    As you know and have well described, it's a bug and should be addressd - period. It is not an OS or machine issue.

                    Peter
                    Peter
                    AlphaBase Solutions, LLC

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


                    Comment


                      #25
                      RE: Buggy Report Writer

                      Thank you! Finally someone agrees with me.

                      I appreciate the feedback.

                      Brandi

                      Comment


                        #26
                        RE: Buggy Report Writer

                        I believe it is a defect if it impairs my work.

                        If you were driving down the street, and your car ran out of steam every two-five minutes and you had to turn it off, and then turn it back on so that it would start rolling forward again, would you consider that a defect?

                        B

                        Comment


                          #27
                          RE: Buggy Report Writer

                          With that analogy, Microsoft Windows is a disaster. Some time ago, Microsoft regularly suggested rebooting at least once a day to clean up memory problems. A car that crashs twice a day unless you shut it off and restart it would certainly be defective. But we seem to consider that acceptable in computers. No wonder Linux is getting a toe hold.

                          While I agree that the apparent lockup is a problem, it is not restricted to Alpha. I have seen the same behavior in many programs. Some are much worse. Any operation that puts a lot of data into memory has the potential for memory issues. Saving and clearing the memory will usually clear up the issue. How many people can you put in your car until someone has to get out or the car is overloaded? That is a better analogy on the memory issue.

                          Jerry

                          Comment


                            #28
                            RE: Buggy Report Writer

                            I don't see the same behavior in other programs. My development activities span across several development platforms and developer studio products, as well as just huge aps, including Delphi 7 and 8, Visual Studio, Visual Studio .NET, Microsoft Visio, and ALPHA 5 v4.5, (not to mention rpg games) and none of these memory hogs causes me the same issue as alpha 5.

                            And if you will go back and read the thread completely you will notice I said that if I open Alpha 5 for the first time, and begin working in the report writer, within 2 to 5 minutes it breaks down AGAIN. This can even be after a complete reboot of my system, so I am not going to let everyone COP out this issue as a Windows problem. I would believe it if it didn't happen on several computers with several different windows platforms, some of which are very powerful machines.

                            Now don't get me wrong, I am not sticking up for Windows, I am right in line with everyone else telling you that Windows is a piece of crap, but that is NOT the issue here. Even running memory and cache management software I have the same problem. I don't have issues with other programs crashing. Just Alpha 5.

                            Lets try this analogy. Get a new pen, write three words, run out of ink, replace the ink cartridge, write three words, run out of ink replace the ink cartridge.

                            Gets to be rather expensive. Just like my time.

                            B

                            Comment


                              #29
                              RE: Buggy Report Writer

                              Brandi,

                              ""Every time I make an edit or resize a field my ability to continue editing the report becomes hindered. After doing a few actions, the report writer will just stop working. It won't let me move anything around, or resize anything, or copy and paste.""

                              Same here. I have several complex (lots of fields) and I have run into the same exact problems. I always compact after I make several revisions, and before going on to do anything else. In the report writer, when things quit working, I usually close Alpha5 and restart. Up until now I guess I just considered it a "quirk" and worked around it.

                              I have found if you continue to "force" things in the report writer, it will corrupt something. That "something" will not always be obvious until you go to print 1500 pages (in groups of 25) on a tight deadline.

                              In my opinion, I think Alpha5 still has some memory leaks here and there. Why? Start Alpha5, take note (in XP do a ctrl/alt/del) in the task manager of the size memory requirement. Now use the program and open, close a few forms etc. Look again at the amount of memory. Now design, or use an app all day, and look at what it is using for memory.

                              I have had my app open lately doing a lot of printing. One report based on one query returning about 900 records. The memory use has climbed to about 162meg. I think this can and does cause problems with average machines. I have 1 gig of memory and there is no reason that one program should continue to grab memory and not release it.
                              Even If I'm just entering records and doing nothing else, memory usage climbs throughout the day until various aspects of the program start to act up.

                              I don't mean to hack anyone off, I think alpha5 is a good program and will continue to use it. I think things are still a little rough around the edges.

                              Phil

                              Comment


                                #30
                                RE: Buggy Report Writer

                                Phil,

                                what you're describing illustrates what I was trying to tell Brandi earlier in this thread. If you have a complex report and you can cause unexplained behavior (or memory usage) by following a specific sequence I think it would be helpful if it could be sent forward to Alpha so they can see it too. -- tom

                                Comment

                                Working...
                                X