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

Email current report as an email

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

    #16
    Re: Email current report as an email

    Oh my goodness, I feel like I could write a book on this! Like Tom, we use this EXTENSIVELY!! But as Dave says, requires setup!
    Call the report as a preview
    close report and save the report to a defined file name
    call an xdialog email client and populate the eto, ecc,ebcc,esubj,emess,eattachment fields with variables for each collected in the script
    email the report using email_smtp_open(), email_smpt_send(), email_smtp_close()

    I have battled all the email methods over 10 years and this is the only email strategy that really works across multiple user platforms, reliably.
    Mike W
    __________________________
    "I rebel in at least small things to express to the world that I have not completely surrendered"

    Comment


      #17
      Re: Email current report as an email

      Firstly
      Maybe I've been lucky, I do only have 5 clients emailing invoices and I used email_send2 purely because thats what I first got working on my side and has been problem free for a couple of years. With both Mike AND Tom concurring on smtp I will definitely revise my method for future.
      So I'm happy to follow that advice.

      Secondly,
      this post was not about email reliabilty or method but about conveniently using the view report dialog with an option to email (ie. as Mike put it..close report and save the report to a defined file name, call an xdialog email client and populate) .. from that option with no further user action.
      That is what I addressed in my suggestion, not any specific method of emailing.

      Does anyone have other suggestions for that?
      see post #1

      Comment


        #18
        Re: Email current report as an email

        This could be done as a dialog, asking for the name of the report to be "saved as", then if you want to preview it, do a "sys_open()" of the pdf file, which will open acrobat so you can view it. Once you have the name of the report entered, the e-mail code is just a simple task that sends the report as an attachment.

        Comment


          #19
          Re: Email current report as an email

          I found this. I forgot that I sent an email setup example to a MB friend to check the robustness of our strategy. I change it to not have our specific strategy but instead to have the email parameters in a table (sys_var) for the email_smtp_open,send,close() methods. I believe this exemplifies some ideas that have been written in this post.
          Attached Files
          Mike W
          __________________________
          "I rebel in at least small things to express to the world that I have not completely surrendered"

          Comment


            #20
            Re: Email current report as an email

            show off!

            Comment


              #21
              Re: Email current report as an email

              The example I posted is not the remarkable thing. I have hundreds of saved examples from me making them to ask for help, for others as examples, and many, many from others who have posted examples on the MB. The remarkable thing is I remembered that I though that I might that possibly I had an example.... and that I actually found it! I really need an application to catalog all my example applications.
              Mike W
              __________________________
              "I rebel in at least small things to express to the world that I have not completely surrendered"

              Comment


                #22
                Re: Email current report as an email

                Originally posted by Mike Wilson View Post
                I found this. I forgot that I sent an email setup example to a MB friend to check the robustness of our strategy. I change it to not have our specific strategy but instead to have the email parameters in a table (sys_var) for the email_smtp_open,send,close() methods. I believe this exemplifies some ideas that have been written in this post.
                Thanks Mike. This is quite a gift. I have learned more from your contribution about email than any of the other posts so far.

                Rich

                Comment

                Working...
                X