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

Blank report results on build 4369_3712

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

    Blank report results on build 4369_3712

    We have recently upgraded our runtimes to the latest version (4369_3712) and noticed that our reports are started to produce errors when sent to a printer or just blank pages when previewing them. Going back to original installation build (3674) gets rid of the problem but causes issues with other databases getting duplicate records on reports (which is why we upgraded to the latest patch in the first place).

    Having done a quick search it looks like we aren't alone but all I'm seeing are instructions on downloading an older build to remove the issue. Has anybody found out what is causing the issue and a way to fix it? We'd like to stay at the current build if we can or at least find one that doesn't give us duplicate records on our database reports.

    #2
    Re: Blank report results on build 4369_3712

    Hi Joseph,

    Do you get the same errors with the reports in Alphasports? If you don't, then I suspect the problem could be the way your reports are designed.
    Regards
    Keith Hubert
    Alpha Guild Member
    London.
    KHDB Management Systems
    Skype = keith.hubert


    For your day-to-day Needs, you Need an Alpha Database!

    Comment


      #3
      Re: Blank report results on build 4369_3712

      Before jumping further:
      Was your application built in v10 or 10.5? If it was built in earlier versions, there may have been a change in set designs that would need to be addressed.
      Dave Mason
      [email protected]
      Skype is dave.mason46

      Comment


        #4
        Re: Blank report results on build 4369_3712

        It was built in 10.5

        We have 20 or so databases written in 10.5 and every one of them is experiencing the same issue since applying the patch.

        Comment


          #5
          Re: Blank report results on build 4369_3712

          We don't have the alpha sports sample but the issue occurs across all of our various databases (about 20 or so).

          Comment


            #6
            Re: Blank report results on build 4369_3712

            Joseph,

            You should have AlphaSports in the Samples subfolder in your Alpha Five program files folder. i.e. in the folder where you installed the developer version of Alpha Five v10.5.

            When you say "databases" are you referring to DBF's ? i.e. tables ?

            Comment


              #7
              Re: Blank report results on build 4369_3712

              These are all ADB's with multiple DBF's as part of them.

              I don't have the same issue with the Alpha Sports database but the reports there are much less complex than what we are running. Also the issue goes away when we install build 4260_3685. However the duplicate items on reports issue that the latest build fixed has returned with going back to the previous build.

              Comment


                #8
                Re: Blank report results on build 4369_3712

                If AlphaSports produces accurate reports using the latest patch that's a good indicator the download / installation of the patch was successful... ruling out corruption in transit.

                If your reports are misbehaving due to a bug in Alpha Five its unlikely the bug will be fixed. No more patches to V10.5 are anticipated.

                You might try downloading the trial vers of A5v11 to see if it runs the reports correctly. If not a bug report could be submitted for v11.

                Comment


                  #9
                  Re: Blank report results on build 4369_3712

                  V11 fixes the blank page issue but breaks a few other things that can be repaired. We may have to go that route.

                  Comment


                    #10
                    Re: Blank report results on build 4369_3712

                    Default Blank report results on build 4369_3712 Did you ever get your blank reports to work? I have the same build, and have had a report stop working, and only produce a blank report. I was hoping you might be able to help.

                    Comment


                      #11
                      Re: Blank report results on build 4369_3712

                      just a thought.
                      just went from v8 to v12
                      two reports went blank after v8 - finally traced to set design where v8 must have been real lenient. Once taken care of, reports print fine. of course we made real sure that data should be in the reports first.
                      Dave Mason
                      [email protected]
                      Skype is dave.mason46

                      Comment


                        #12
                        Re: Blank report results on build 4369_3712

                        Open a default browse for the set and see what data is available.

                        Edit the set linkage until you see the proper data.

                        Use a query to test the filter and other used in the report.
                        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


                          #13
                          Re: Blank report results on build 4369_3712

                          Linda,
                          We're having the same issue. Just updated, reluctantly, and now seeing the same thing on a new user's machine. Plus it causes a hang. Not sure if it's a Win 8 issue, the update, or the user's machine A5printerv4 being set to LPT. Have heard that the port needs to be nul.

                          Comment

                          Working...
                          X