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

saving as .pdf

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

    saving as .pdf

    I am having trouble saving the output of a report in A5v5 as a .pdf (same thing happens when I try to save it as a .rtf). When I preview the report to screen all appears ok. When I choose "save as" and try to make a .pdf, the initial value of one of the fields is repeated for all subsequent rows on the report. Anybody have this problem? Am I tying up too much memory somehow? I did try rebooting and opening only A5 (no other programs) and got the same result.

    Thanks for any advice.

    -Bill

    #2
    RE: saving as .pdf

    Bill:

    I assume that the report will print properly. You only indicated that it looked ok in the preview.

    I've not every had a problem printing a .pdf file.

    Bob

    Comment


      #3
      RE: saving as .pdf

      It won't print correctly from v5 (I have been able to print it from v4.5). The problem is that calculated fields on the report either repeat the value that was calculated for the first record, or they simply print the calc field name.

      Comment


        #4
        RE: saving as .pdf

        Bill:

        The problem appears to be in the report and not with the .pdf function.

        You may need to relook at how the cal fields are created. If you have some examples it might be easier to see where the problem is.

        Bob

        Comment


          #5
          RE: saving as .pdf

          Here's one of the calc fields that I am having the problem with: alltrim(lookupc("f", lookupn("f", Pic_Link->Pic_Id, "photog_id", "pictures", "pic_id"), "submtr", "photog", "photog_id"))

          I think the problem may be memory related, because the report works fine in A5v4.5 (in either print or preview mode) and will work fine in A5v5 in either print or preview mode (i.e. either report.preview("pub_log3") or report.print("pub_log3"). The problem happens when I do a report.preview("pub_log3") - which produces the correct results on the screen - and then choose "save as" from the file pull-down menu. Saving it as .pdf or .rtd produces the error.

          Comment


            #6
            RE: saving as .pdf

            Bill:

            Why do a SAVE AS. Just print it to the a .pdf file. Hit the print icon and select the PDF driver which should be a part of your printers.

            I've never had a problem doing this. Then you can attach the file to an email or just open it in Arcobat.

            Bob

            Comment


              #7
              RE: saving as .pdf

              Wow!!

              This is quite an expression:

              alltrim(lookupc("f", lookupn("f", Pic_Link->Pic_Id, "photog_id", "pictures", "pic_id"), "submtr", "photog", "photog_id"))

              And you say it works! I thought I've asked a lot from Alpha.

              Tom

              Comment


                #8
                RE: saving as .pdf

                Bob,

                I don't think the pdf driver installed with Alpha Five can be used as you describe. Perhaps you have another pdf driver that's kicking in?

                -- tom

                Comment


                  #9
                  RE: saving as .pdf

                  Actually, I do get the same result if I choose print and choose the pdf driver.

                  Comment


                    #10
                    RE: saving as .pdf

                    I don't believe that I have any other pdf driver installed. And I have used this approach with other reports (i.e. a button's on_push will kick off a script that concludes with a report.preview("report_name") - the user then has the option of reviewing the report on screen or printing it (using the file pull-down menu in v4.5) or saving as (in v5).

                    Comment


                      #11
                      RE: saving as .pdf

                      This used to be quite slow (before v4.5). Embedding a lookup within another lookup (when you don't have the key for what you want to print) does work though, and since v4.5 it has not taken all that long either. In the report that I am having trouble with, this calc field has no problem printing to screen or to paper - I just can't save the results as a pdf or rtf file.

                      Comment

                      Working...
                      X