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

many blank pages after 1st page prints

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

    many blank pages after 1st page prints

    i have a report that prints fine on my pc running v4.5. i took it to the client running 4.03 (i think), and the 1st page prints fine and then the rest of the pages are blank, and there are an almost infinite number of blank pages.
    what could cause this not to work in v4.03?

    #2
    RE: many blank pages after 1st page prints

    Instead of differences between 4.5 and 4.03 I'd look first at differences between your pc and printer and the client's.

    Is the report layout defined for a particular printer or does it use the current windows default printer? If you defined it for a particular printer and that printer is not setup and installed at the client you could have the kinds of problems you're describing.

    Do the two printers have identical non-printable areas? Most modern laser and inkjet printers have nonprintable areas along all four edges. The dimensions of these nonprintable areas differ from printer to printer. The symptoms you're seeing remind me of situations I've had where my report layout would not 'fit' within the physical dimensions of the 'printable' region on my client's printer, even though it worked fine on my own (older) printer. This kind of issue can be solved by changing the layout to increase the margins along all four edges.

    Comment


      #3
      RE: many blank pages after 1st page prints

      they're both lasers, tom. i will check it out. thanks for the idea.

      Comment


        #4
        RE: many blank pages after 1st page prints

        Another test that can be run on one page reports is to select the "Shrink to fit" option. This will give you an idea of how big the margins need to be. I recently ran into a situation where right and left margins were 0.5 and top/bottom were 0.75 but the report still printed on multiple pages (all but the first were blank). After setting "Shrink to fit", the report looked just fine so I left it that way. (Yes, it will probably come back to haunt me later.)

        Comment


          #5
          RE: many blank pages after 1st page prints

          yes, i already checked that box on my report here. i am going to take the changes to the client tomorrow and see what happens

          thansk

          Comment


            #6
            RE: many blank pages after 1st page prints

            i found out what ws causing this, print 1 page and then an infinite number of blank pages. in the report under report properties on the head/foot tab, i had a check next to has continuation header under the headers section. removed the check and it prints fine at both locations. why it worked at home and not at my client's is beyond me. set up the same printers on both pc's and everything. just would not work at my client's with that checked.

            Comment

            Working...
            X