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

Code after "Save Dialog" not running in AfterDialogValidate - only in browser...

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

    Code after "Save Dialog" not running in AfterDialogValidate - only in browser...

    Hi
    I have a dialog used for adding/editing records in a grid. The DB is mySql.
    In that dialog, i have the following code in my afterDialogValidate
    Code:
    function afterDialogValidate as v (e as p)
    
    ExecuteServerSideAction("Save Data::SaveDialog")
    
    dim myargs as sql::Arguments
    myargs.add("whatOrderID", e.dataSubmitted.OrderID )
    dim FileName as C
    FileName = "C:\MyCustomer\Reports\Res"
    FileNAme = FileName + alltrim(str(e.dataSubmitted.OrderID))+".pdf"
    dim options as p
    options.filter = "OrderID = :whatOrderID"
    report.SaveAs("Daily Confirmation", "PDF", "", "", FileName, .f., options, myargs)
    'debug(1)
    dim curEmail as C = e.dataSubmitted.CustomerEMail
    dim curSubject as C
    dim curMessage as C
    
    curSubject = "Reservation "+alltrim(str(e.DataSubmitted.OrderID))
    curMessage = "Dear "+e.dataSubmitted.Contact + Crlf()
    curMessage = curMessage + "Please find attached the details of your Reservation"+crlf(2)
    
    dim pm as P
    dim ps as P
    if (email_smtp_open(ps, myserver, 25, myUser, myPassword)) then
        pm.to = curEMail
        pm.from = "someemailaddress"
        pm.subject = curSubject
        pm.message = curMessage
        pm.attachments = FileName
        email_smtp_send(pm, ps)
    end if
    email_smtp_close(ps)
    In working preview, the code works great. Record is saved in the DB, PDF report gets generated in due place, and the generated report is emailed.
    When running in the browser, after publishing the project, clicking on submit does not seem to do anything ( i.e dialog stays put, and stays dirty ) but noticed the record is saved in the DB. The rest of the code does not run, and the dialog doesn't close ( which is obvious if the code didn't run )

    Any clues?
    Thanks,
    Jaime

    #2
    Re: Code after "Save Dialog" not running in AfterDialogValidate - only in browser...

    One thing you can do to debug the script when it is running in the browser is to add code to the afterDialogValidate script to write to text files.
    Put the command in three or four places throughout the script, and write variable values to each files. Then look at the files after you run the script to see how far the script got.
    Hope this helps.
    Jay
    Jay Talbott
    Lexington, KY

    Comment


      #3
      Re: Code after "Save Dialog" not running in AfterDialogValidate - only in browser...

      Thanks Jay.
      Of course that's what i did before posting.
      After some more testing, the problem is *nothing* runs after the "Save Dialog" action, which if you come to think of it, is logical - in the action itself, i selected "Edit the record just entered" in the properties since it's the closest to what i want, but in fact what i would want to see there is "continue execution" or something like that...
      What puzzles me is how come this code works in working preview ( all the code in the afterdialogvalidate runs even what's after the "Save" ) then closes the dialog and, as expected, brings me back to the calling grid, while in the browser code just stops after the "Save" action...

      Jaime

      Comment


        #4
        Re: Code after "Save Dialog" not running in AfterDialogValidate - only in browser...

        Then would it work to move this line:
        ExecuteServerSideAction("Save Data::SaveDialog")

        down to the bottom of the script?
        Jay
        Jay Talbott
        Lexington, KY

        Comment


          #5
          Re: Code after "Save Dialog" not running in AfterDialogValidate - only in browser...

          Thanks Jay.
          Finally found the problem, which i don't know how to solve. The problem is that the line

          report.SaveAs("Daily Confirmation", "PDF", "", "", FileName, .f., options, myargs)

          does not run in the browser, and stops execution right there, so i guess this command is not supported other than in the desktop? In that case, i really don't know how to just email a pdf report upon saving...

          Comment


            #6
            Re: Code after "Save Dialog" not running in AfterDialogValidate - only in browser...

            This quote:
            Hi Dave,

            I recently had issues with this command.

            After I got it figured out, I posted my resolution.

            Hope this helps.

            Gregg

            :Report.SaveAs("reportname","PDF","","","c:\reports\filename.pdf",.F.) works great for desktop apps, but fails when being called from a .a5w page.
            :Report.SaveAs("reportname@c:\datadir\tablename.ddd","PDF","","","c:\report\filename.pdf",.F.) works great for desktop apps and when being call from a .a5w page.
            is from this thread:
            http://msgboard.alphasoftware.com/al...ead.php?103073

            Hope this helps.
            Jay
            Jay Talbott
            Lexington, KY

            Comment


              #7
              Re: Code after "Save Dialog" not running in AfterDialogValidate - only in browser...

              Thanks! In fact i saw that thread and forgot about it.
              Still, i am using mySQL, and as per Steve Wood's advice, i tried

              Report.SaveAs("report name@c:\A5WebRoot\MyCustomer\project...t\filename.pdf",.F.)

              with no success...

              Comment


                #8
                Re: Code after "Save Dialog" not running in AfterDialogValidate - only in browser...

                Ok, got it finally running using A5W_Report_SaveAs .
                Still , this doesn't work as expected in the browser. First a small recapitulation of the relevant code:
                Code:
                ExecuteServerSideAction("Save Data::SaveDialog")
                dim myargs as sql::Arguments
                myargs.add("whatOrderID", e.dataSubmitted.OrderID )
                dim FileName as C
                When running in the browser, e.dataSubmitted.OrderID is empty ( in working preview the newly generated OrderID is in there ) so the rest of the code runs with an empty value for OrderID...Why is that?

                Comment

                Working...
                X