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

Crashing when Previewing a report

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

    Crashing when Previewing a report

    I have a Toshiba Satellite, P-III, 650MHz with a S3 Inc. Savage/IX w/MW video card.

    For some reason, when I do a maximized print preview of certain reports, the computer locks up completely and has to be turned off.

    Yet, other reports work just fine. I have to put text on the screen warning of which reports can be opened maximized and which cannot.

    Anybody have any ideas?
    Is this a bug?

    Ron
    Alpha 5 Version 11
    AA Build 2999, Build 4269, Current Build
    DBF's and MySql
    Desktop, Web on the Desktop and WEB

    Ron Anusiewicz

    #2
    RE: Crashing when Previewing a report

    I have a similar machine. If I set the resolution to 800 by 600, I can preview reports without the lockup you have also encountered.

    Search the board. I don't think anyone came up with a fix.
    There can be only one.

    Comment


      #3
      RE: Crashing when Previewing a report

      Ron,

      This seems to be related to the S3 chipset. I have an app that does exactly the same thing on only one computer. That computer uses the S3 video chip. The app works fine on all other computers. No good solution that I know of, especially with a laptop.

      Jerry

      Comment


        #4
        RE: Crashing when Previewing a report

        Hi Guys,

        The S3 chip has been a thorn in our side since it came out. I met an
        engineer from Diamond a few years (S3 is their brainchild) and asked
        him if there is a workaround or new drivers to solve the problem, his
        answer was an emphatic NO. The S3 chip usually interferes with COM 4
        when it uses IRQ3 and 2EM memory location. Hence, I have made it a
        practice to put non-PNP modems on COM2/IRQ3 and it severely reduced
        the conflict, but not totally. I don't really like to do this, because
        COM2 is usually accessible externally for the user to connect other
        periphals. My solution is to replace the video adaptor, or in the
        case of it being an integral part of the mainboard, to disable it in
        the BIOS and then add a non-S3 video display card in an appropriate
        slot.

        efs

        Comment


          #5
          RE: Crashing when Previewing a report

          Thanks for your help.

          What I've learned is that my reports printed in landscape mode are "OK". It's the reports previewed in portrait mode that result in the computer locking up.

          Switching the display to 800 x 600 does prevent the locking up, but then my forms go off the sides of the screen.

          Computers can be such a pain.

          Ron
          Alpha 5 Version 11
          AA Build 2999, Build 4269, Current Build
          DBF's and MySql
          Desktop, Web on the Desktop and WEB

          Ron Anusiewicz

          Comment


            #6
            RE: Crashing when Previewing a report

            I found a cure for this problem. After searching this board, I found a post from Ira which I really didn't understand. Now I do.

            Go to

            Settings
            Control Panel
            Display
            Settings
            Advanced
            Performance

            You should have a screen with an adjustment for hardware acceleration. The choices are None to Full. There are 4 settings. The default setting for my Tosiba is full.

            If None is 1 and Full is 4, I had to change my setting to 2.
            Now I can run the screen at 1024 x 768 and can print preview maximized without locking up the computer.

            I'm not sure what I lost in performance, but this is better than running at 800 x 600 or trying to remember not to do print previews maximized.

            I hope this helps.

            Ron
            Alpha 5 Version 11
            AA Build 2999, Build 4269, Current Build
            DBF's and MySql
            Desktop, Web on the Desktop and WEB

            Ron Anusiewicz

            Comment


              #7
              RE: Crashing when Previewing a report

              Ron, thanks for taking the time to post the follow up solution. It's the kind of thing that could help others in the future.

              -- tom

              Comment


                #8
                RE: Crashing when Previewing a report

                Hi Ron,

                Thanks a million, I love it !
                efs

                Comment


                  #9
                  RE: Crashing when Previewing a report

                  Ronald and Ira,

                  THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU!!!

                  This solved a problem I have been living with for over a year. Life is good!

                  Sherrill

                  Comment


                    #10
                    RE: Crashing when Previewing a report

                    Hi Guys,

                    I mistakenly referred to the starting memory location as 2Em, it should
                    have read 2e8. Unfortunately I just upgraded to a new and faster
                    system with the video display adaptor built onto the mainboard. The
                    BIOS allows disabling that feature but does not provide ISA slots for
                    for my old 32 Meg video card and modem. What is more, I now have to use
                    a Winmodem (no ISA slot for it either) and it seems like my 1 Gig
                    system is running like an old 286 when on the net. All other aspects
                    seem good except the 8 Meg card refreshes very slow. Please don't make
                    the same mistake.

                    efs

                    Comment

                    Working...
                    X