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

Cannot get Context.Request.GetTempFileName() to work

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

    Cannot get Context.Request.GetTempFileName() to work

    I am trying to get Context.Request.GetTempFileName to work. Alpha's documentation does not provide an example, and as such, I am floundering.

    Does anyone have an example that works, and would be willing to share the code?
    Thank you.
    Jay
    Jay Talbott
    Lexington, KY


    #2
    dim fn as c
    fn = Context.Request.GetTempFileName()
    'do something with fn
    'the file will automatically be deleted from the server at the end of the request processing

    Lenny Forziati
    Vice President, Internet Products and Technical Services
    Alpha Software Corporation

    Comment


      #3
      Lenny,
      Thank you for the quick response. I am trying to use it in this context (all bad puns intended)

      Relevant lines are in red

      function emailReport as c (e as p)
      debug(1)
      DIM vFilter AS c = ""
      DIM args AS sql::Arguments
      DIM Options AS p
      DIM printOptions AS p
      DIM js AS c = ""
      DIM result as L = .F.
      args.Set("invoiceNumber",4192)
      reportname = ""
      saveAS = "PDF"
      filter = ""
      order = ""
      filename = ""
      reportname = "C:\A5Webroot\sdat\invoice.a5rpt"
      vc_path = "C:\A5Webroot\ReportFiles"
      myFile = vc_path + "\invoice_"+alltrim(str(toseconds(time())))+".PDF"
      fn = Context.Request.GetTempFileName("pdf")
      fn = a5w_report_saveAs(reportName,saveAs,filter,order,myFile,null_value(),null_value(),args)

      DIM pm AS p
      DIM ps AS p
      IF (email_smtp_open(ps,"smtp.gmail.com",587,"smtp", "password","TLS")) THEN
      pm.from = "xxxxx@yahoo.com"
      pm.headers = "Reply-To: xxxxx@yahoo.com"
      pm.cc = pm.cc +", "+pm.from
      pm.from_alias = "Jay TTT" ' e.dataSubmitted.customerName '
      pm.subject = "my subject" 'e.dataSubmitted.emailSubject '
      pm.message = "this is the message" 'e.dataSubmitted.emailmessage '
      pm.attachments = fn
      result = email_smtp_send(pm, ps)
      END IF
      email_smtp_close(ps)
      DIM emailDate AS c = format_data(date(),"12-")
      IF result = .T. THEN
      js = "alert('email successfully sent');"
      ELSE
      js = "alert('emailfailed');"
      END IF
      endScript:
      emailReport = js
      end function
      I keep getting this error:

      Error executing Ajax callback. Error executing Ajax callback function 'emailReport': command: fn = Context.Request.GetTempFileName("pdf") Property not found

      I get this with or without "pdf" added to Context.Request.GetTempFileName()

      Thoughts?

      Thanks for your time.
      Jay
      Last edited by Lenny Forziati; 04-12-2021, 06:13 PM. Reason: removed personal info (email addresses)
      Jay Talbott
      Lexington, KY

      Comment


        #4
        The correct method is actually Context.Request.GetRequestTempFileName() I'm osrry I didn't notice that in your original post, and even reused the error in my reply.

        Also you should fully replace myFile with fn. The way you have it currently, myFile will be created to hold the report, and that file will NOT be automatically removed at the end of the request.

        Lenny Forziati
        Vice President, Internet Products and Technical Services
        Alpha Software Corporation

        Comment


          #5
          How timely. Then why does build 5566, using this:

          tempfilename = Request.GetRequestTempFileName("PDF")
          filename = "Chemical_Inventory"
          a5w_report_saveAs(reportName,saveAs,filter,order,tempfilename,global_variables(),printOptions,args,options)
          ablob = file.to_blob(tempfilename)

          Produce this on-screen (when previous builds did not, and I have other reports using the same model)?

          Snap0.png


          -Steve
          sigpic

          Comment


            #6
            So, I used the above code, but changed the line to use the context object:

            tempfilename = Context.Request.GetRequestTempFileName("PDF")

            Now this error:

            Snap1.png

            and I confirm that the path does not exist:

            Snap2.png


            -Steve
            sigpic

            Comment


              #7
              I'm not as advanced as you guys but I bet it has something to do with the number of write attempts by AA.
              Gregg
              https://paiza.io is a great site to test and share sql code

              Comment


                #8
                I think it does too. The error message says it can't find a path, and I show that the path is not there.
                -Steve
                sigpic

                Comment


                  #9
                  It's a shame we can't take that error and create the path for it.
                  Gregg
                  https://paiza.io is a great site to test and share sql code

                  Comment


                    #10
                    Actually, I did add the folder manually to the path indicated a number of times today while testing "locally" using Live Test (NOT Live Preview).
                    The only problem with adding the folder, and in my case it ended in req_1, is that true to the intent, the folder gets deleted, and has to be re-added for each test. But it does work.
                    I do not believe this will be a problem when published to the server.

                    Jay
                    Jay Talbott
                    Lexington, KY

                    Comment


                      #11
                      Jay, with that thought in mind, do you think the folder can be created as part of the error handling of on error goto ?
                      Gregg
                      https://paiza.io is a great site to test and share sql code

                      Comment


                        #12
                        That might work, but again, I think this issue is limited to local testing. On the server, it should not be an issue.

                        Jay
                        Jay Talbott
                        Lexington, KY

                        Comment


                          #13
                          I would think you can parse the temp file name, get the directory, create if it doesn't exist. But I've not tried it. I have a couple hundred of these throughout my app and no way am I going to accept that I have to go do that.
                          -Steve
                          sigpic

                          Comment


                            #14
                            I would think parsing them programmatically is relatively simple.
                            I would certainly add it in to the error handling just to avoid the hassle while developing.
                            Gregg
                            https://paiza.io is a great site to test and share sql code

                            Comment


                              #15
                              As an update to this, I did get the report to send via email when testing from LiveTest (NOT Live Preview) using Alpha Cloud. However, when I publish to Alpha Cloud and try it, I get this message:

                              Error executing Ajax callback. Error executing Ajax callback function 'emailWithReport ': SQLReporting 9 - Could not create ResultSet from DataSource definition. Could not execute query against Database. Error reported was: Not currently connected to Database at line: 850

                              In the words of Rosanne Rosanadana, "Never mind". I had a connections string issue. This now works well.


                              Thanks,
                              Jay

                              Last edited by Jay Talbott; 05-13-2021, 04:32 PM.
                              Jay Talbott
                              Lexington, KY

                              Comment

                              Working...
                              X