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
Devcon 2020 Goes Virtual! LEARN MORE >

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

letter.saveas() problem trapping empty query

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    letter.saveas() problem trapping empty query

    I've been using letter.saveas() and report.saveas() to create a PDF to email invoices to customers, but have hit a problem where alpha doesn't return an error if there are no records in the report/letter. I know I can trap the record count from the query prior to creating the letter, but is there no way to trap an error on execution of the letter.saveas() command?

    I'm not sure if a simple record count on the query is going to be good enough to trap any error as a customer (running on a network optimised system) executed a run on Friday which created an empty report, but when I tried to replicate the problem from a backup the report was correctly generated.
    Tags: None
    #2
    Re: letter.saveas() problem trapping empty query

    In Alpha terms it is not an error that no records fit the query specified in the .saveas() method. You'll have to be a little clearer about the situation when the letter was generated Friday vs the backup.
    There can be only one.

    Comment

      #3
      Re: letter.saveas() problem trapping empty query

      Stan, thanks for the quick response. I wish I could give more details, but the client is unaware of any problems during the run. It is possible that the record was open when building the report, but I'm not sure if that would cause a problem. Alternatively, there could have been a network problem.

      This is a little frustrating as Alpha is aware that there are 'no pages in the layout', but doesn't return anything other than a blank report. report.preview() even throws up a message box, but again, I can't find a way to trap it!

      Comment

        #4
        Re: letter.saveas() problem trapping empty query

        A little experimentation leads me to believe the letter.saveas() actually does throw an error if there are no records (No pages in layout.). Don't do letters so I didn't realize that.

        The error code is dynamic and will vary each pass but it will be in the range 16000 to 16999. You should be able to trap that.
        There can be only one.

        Comment

          #5
          Re: letter.saveas() problem trapping empty query

          I guess I'm confused. "<OBJECT>.saveas()" does not have any method to trap for no records. However Alpha has provided a plethora of functions including the strangely named a5_get_records_in_query(). So there would be no extra code to trap for no records, if <OBJECT>.saveas() returned "any thing" for no records you would still need the if statement and you would still get the blank report (unless they completely rewrite it).



          If (a5_get_records_in_query("YourTableorSet",YourFilter")=0) than
          msgbox("No records to print")
          else
          <OBJECT>.saveas(........)
          end if


          I realize that you are concerned about a query but it is what we have. Perhaps the filter was wrong.

          Comment

            #6
            Re: letter.saveas() problem trapping empty query

            By the look of things there's no way to reliably trap if a report.saveas() or letter.saveas() finds no records - and in this instance it should have found several - so I have taken a different path to check for blank results. I have modified the calling script to check the filesize of the report/letter and to bypass the emailing phase if the pdf is too small to be valid...

            Code:
            :Letter.SaveAs("WW_CLEAN_DATES","PDF",query.filter,query.order,a5.get_path()+"\letters\Cleandates_"+my_CID2+".pdf",.F.)
if file.size(a5.get_path()+"\letters\Cleandates_"+my_CID2+".pdf") < 4000 then
'execute error routines
else
'execute send routines
end if
            I believe this will trap all instances of null reports/letters for this particular scenario.

            Thanks to Stan and Allen for their responses.

            Comment

            Previous template Next
            Working...
            X