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

Published Linked Subreport Doesn't Print

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

    Published Linked Subreport Doesn't Print

    I'm on 8368-5659 and have a report based on a DBF set (i.e. report shows under the Reports tab in Control Panel). This report contains a linked subreport. Problem is: I am having a devil of a time publishing the main report so that the linked subreport actually prints.

    When I try to "Preview" the main report directly in Control Panel it functions fine; i.e. the records that should be in the linked subreport show. When I publish everything to the Local Webroot, however, the subreport doesn't print anything (although the main report prints fine). The records that should print in the subreport are in the DBF files, obviously, since they appear in Preview and the Preview and Local Webroot use the same source. I first noticed this non-printing issue when I tried to publish to my remote host, but I tried to isolate the problem by publishing/printing locally and it still happens (or doesn't) and can't figure out what's going on. I've linked the main report to the subreport numerous times (using both the "Refresh LInked Report" properties tab selection AND explicitly picking it again. No go.

    Has anyone run into this sort of issue before? Any ideas appreciated.



    Norman

    #2
    might depend on several things - could be a shrink or grow issue with the area the data is in, if its in a group footer or not (data getting pushed out) and lastly people might need to know what version of AA you are running as it could be a bug from the past or something new introduced during an update. Definitely need more info. I think if you used the northwind db and posted the report file maybe someone could help. Reports, are tough to troubleshoot from a distance. You might want to consider converting/IMPORT it to a web project report from the control panel and work on it that way. I cannot remember all the benefits but I never use the control panel for reports anymore.
    NWCOPRO: Nuisance Wildlife Control Software My Application: http://www.nwcopro.com "Without forgetting, we would have no memory at all...now what was I saying?"

    Comment


      #3
      I believe what you're asking for is in my OP (AA 8368-5659), unless you're asking for something else. The report itself is of master-detail type, the subreport runs off the detail; Northwind won't work as the source files are DBF.

      Changing to Web Project reports may be something I can do down the road, but this is a legacy app that has been working fine and which I'm copying for another purpose. Strange thing is that, at least on the remote host, the same report will sometimes show the subreport, sometimes won't, and it seems the longer I "wait" before running the report the more likely it is to work. As with many, many things, should I ever figure out what's going on, the answer will seem simple in retrospect, as in "why didn't I see that"? It's just before the fact that's a killer. :)

      Thanks for posting your thoughts.

      Comment


        #4
        There have been a lot of people with reports not printing type errors lately this past year, I did see in the release notes of 8417-5662 that there is a mention of linked sub-reports, maybe it's related, maybe not. As you may know you can go through the release notes and searching for the word "printing" you can see there have been some changes that might affect what your doing and a mention of the recommendation to import to project reports. https://aadocuments.s3.amazonaws.com/ReleaseNotes/releaseNotes_2020_to_present.html
        I know it's not an answer, but I don't think this is just a simple thing to fix like you forgot to tick a box or something.
        NWCOPRO: Nuisance Wildlife Control Software My Application: http://www.nwcopro.com "Without forgetting, we would have no memory at all...now what was I saying?"

        Comment


          #5
          Yea, no, I don't think so either. Also, the subreport, when it does print, skips lines (which is another topic entirely).

          As you suggest, I'll continue to poke around (and read the Release Notes, although I am loathe to switch versions). If all else feels, I'll distill down to a test case and submit as a bug.

          Thanks for the posts.

          Comment

          Working...
          X