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



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

report.saveas project report command format

  • Filter
  • Time
  • Show
Clear All
new posts

  • report.saveas project report command format

    What is the proper command formatting to reference a project report with the new V12 system.

    In my V11 system, I use the following command to generate a PDF version of a report in code.

    filename = report.saveas("bs_period1_filtered", "pdf","guid = '" + session.cashflow.guid + "'","",filename1)
    I have moved the report over to a project report with the same name. But, I get the following error:

    Error:<br>Amyuni Low Level Print:<br>Layout name: [email protected]<br>Layout type: report<br>Error loading Y:\Documents\Dropbox\Private\GKR\cashmax\CashMax Version 2\cashmax alpha project 2\ProjectReport: The system cannot find the file specified.
    Y:\Documents\Dropbox\Private\GKR\cashmax\CashMax Version 2\cashmax alpha project 2\ProjectReport.DBF

  • #2
    Re: report.saveas project report command format

    I'm getting a similar error in v11 3381 - 4096. Its complaining of extra characters in an expression???
    Creating Healthcare Work-Flow Solutions Since 2005


    • #3
      Re: report.saveas project report command format

      you need to give a fully qualified filename for the project report.

      e.g. (assuming your project reports have been published to the webroot)

      dim fn as c 
      fn = request.GetRequestTempFileName(".pdf")
      fn = report.SaveAs(request.applicationRoot + "customerReport.a5rpt","pdf","","",fn)


      • #4
        Re: report.saveas project report command format

        Thanks Selwyn!!! That worked perfectly for my need. Also, I love the request.GetRequestTempFileName(".pdf") function. Makes my code simpler and easier to manage!

        Quick follow up question. The request.GetRequestTempFileName(".pdf") function sets up the temp file so it is deleted as soon as the request is completed. For my use case, this works great for the temporary files I create to combine into a single PDF. But, I would like to use that function and NOT have it delete it. The reason is that after I have generated the multiple temporary files, I combine them into a single PDF file. That PDF file must live beyond the current request because I do a "response.redirect" to open the combined PDF file in the web browser for user display.

        Is there another similar function to request.GetRequestTempFileName(".pdf") that generates a temp file name, but allows it to live beyond the current request.....
        Last edited by dionmccormick; 06-26-2013, 08:24 PM.


        • #5
          Re: report.saveas project report command format

          If this is a web application, you should be using a5w_report_saveas(). report.saveas() is not safe to run in a background thread on the WAS.


          • #6
            Re: report.saveas project report command format

            Excellent point. Thanks for the info!


            • #7
              Re: report.saveas project report command format


              Could someone please explain why using .report.saveas() is not safe to run in a background thread. I tried a5w_report_saveas() in place of report_saveas() and it could not find the report? Also what are the Global Variables referred to in the docs.

              Any info or a direction on where to look for the answers would be greatly appreciated.



              • #8
                Re: report.saveas project report command format

                report.saveas() is not safe to run in a background thread because you could run into threading issues if two requests try to load use the amyuni printer driver at the same time.

                if you look at the system page __a5RunReport.a5w (which is automatically published to the webroot) you will see how Alpha Anywhere handles a request to print a report. you will see that it uses this command (line 470)


                global variables in a web application are any variables dimmed as global in the current executing .a5w page.

                for example


                dim g as global_variables()
                g.myname = "peter"

                'if you were to put code here to print a report the report could refer to 'myname'




                • #9
                  Re: report.saveas project report command format


                  For anyone reading this who, like me, struggled to implement a5w_report_saveAs check out:-


                  Also my twist on the theme for a multi tenanted invoice system (comments welcome):-

                  Dim filename as c = "Invoice_"+e.datasubmitted.invoiceNumber +"("+e.datasubmitted.BizID+").pdf"
                  Dim filepath as c = a5_removetrailingbackslash(request.applicationRoot) +"\sbcsfiles\invoices"+chr(92)+filename

                  dim args as sql::Arguments
                  dim Options as p
                  dim printOptions as p
                  args.set("blank", "")
                  options.propogateErrors = .t.
                  printOptions.blank = ""
                  Dim reportname as c = a5_removetrailingbackslash(request.applicationRoot) +"\Invoice.a5rpt"
                  Dim saveAs as c = "PDF"
                  Dim filter as c = "INVID = "+val(e.datasubmitted.InvID)
                  Dim order as c = ""

                  fn = a5w_report_saveAs(reportName,saveAs,filter,order,filepath,global_variables(),printOptions,args,options)

                  if file.exists(fn)=.f. then
                  Last edited by pcaspa; 10-09-2013, 01:24 AM.