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

AfterInsertRecord trouble

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

    AfterInsertRecord trouble

    I'm quick to admit that the problem may be me, but I'm trying to send an email as an AfterInsertRecord Event on a Grid Component with no luck. I've been successful using the same code (and even more complex) as an AfterUpdateRecord Event that works with no problem. I'm using a grid detail view to enter new records (as I am to update records), but while I don't get an error message of any kind when I enter a new record, the email also doesn't get sent.

    I'm running against SQL Server Express tables--just letting you know in case this has something to do with it... Any help is much appreciated.

    Code:
    function AfterInsertRecord as v (e as p)
    DIM pm as P
    DIM ps as P
    pm.from = "[email protected]"
    pm.from_alias = "CNS WEB"
    pm.to = "[email protected]"
    pm.cc = ""
    pm.bcc = ""
    pm.subject = "Testing"
    pm.message = "Test 1"
    pm.html_message = ""
    pm.attachments = <<%str%
    C:\dev\test.zip
    C:\my documents\report.zip
    %str%
    'optional header fields
    pm.xmailer = "Alpha Mailer"
    pm.lRelated = .F.
    ' send message
    IF email_smtp_open(ps, "smtp1.deltacom.net")
    email_smtp_send(pm, ps)
    END IF
    Email_smtp_close(ps)	
    end function

    #2
    Re: AfterInsertRecord trouble

    Hi Chris,
    I thought I saw the solution but as I was writing it, realized it was not. Perhaps you could try the email_send2(xx) method. This is what I use in many pages.
    Last edited by EricN; 07-30-2009, 12:40 PM.
    Eric

    Alpha Five Websites
    longlivepuppies.com
    socialservicenetwork.com
    -------------------------------------------------
    socialservicenetwork.org

    Comment


      #3
      Re: AfterInsertRecord trouble

      I don't see any problem with your code so I would try the script in a bare A5W page to see if it works there. Side note - maybe its just me but I have always been shy to include anything very complex in a grid event, especially one that has to execute a labor intensive event, like sending an email. The browser has to wait for that event to complete and, if it hangs, so does the browser.

      I've normally used the event to toggle a value in a table, or send out instructions as a 'request' to another process using Watch Directory that will see the instruction and execute it 'off line'. I have more faith that the event will take place and can insert control code to deal with it if if fails.
      Steve Wood
      See my profile on IADN

      Comment


        #4
        Re: AfterInsertRecord trouble

        My understanding is that the email_send() and email_send2() functions don't work when you're developing a strictly web-based app and that you have to use the email_smtp_open(), email_smtp_send(), and email_smtp_close functions instead. Thanks anyway, though.

        Comment


          #5
          Re: AfterInsertRecord trouble

          I use email_send2() almost exclusively on web apps.
          Steve Wood
          See my profile on IADN

          Comment


            #6
            Re: AfterInsertRecord trouble

            Thanks Steve and Eric. And I had apparently misunderstood on the difference on email_send2() and the email_smtp_...() functions.

            There was some code error somewhere else that was keeping this code out for some reason--it's working properly now.

            And Steve, I'm positive there are better ways to do some of the things I'm doing, but I'm still quite new to all of this. That said, those "more complex" things I eluded to were not all that complex if you're at all experienced with this stuff. Thanks again.

            Comment


              #7
              Re: AfterInsertRecord trouble

              not all that complex if you're at all experienced with this stuff
              I was always a better programmer when there were FEWER options in the bag. One big probs I see with V10 is the opportunity for all of us to be all over the map on how we do the same things.
              Steve Wood
              See my profile on IADN

              Comment

              Working...
              X