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 automation addrecord script

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

    email automation addrecord script

    This first part of the addrecord script in the email automation demo.

    'cTable & nRecno are defined automatically
    tInbox = table.open(cTable, FILE_RO_SHARED)
    tInbox.fetch_goto(nRecno)

    Can some one explain how cTable & nRecno are automatically defined? I presume they are variables that alpha5 has dimmed behind the curtain. It makes the script confusing.

    I am guessing that ctable is the a_email table that logs email content and nRecno is any records in the table that meet the Genie filter criteria, or maybe it could be the last record created in the table. The comments do not explain what they are which makes this part of the script a mystery.



    Any insight would be appreciated.
    Tks
    Bob

    #2
    Re: email automation addrecord script

    I tried to break this down in the interactive window but didn't have much success.

    Comment


      #3
      Re: email automation addrecord script

      This is part of the email demo script. I tried it in the interactive window and had it working briefly. ? body
      should return the value of the body field in the last record in the a_email.dbf table. However I am not sure if the problem is nRecno as their is no explanation of how this variable chooses the record from the table. Is their a reason why this script doesn't work in the interactive window?

      DIM tInbox AS P

      tInbox = table.open(cTable, FILE_RO_SHARED)
      tInbox.fetch_goto(nRecno)

      DIM body AS C
      DIM subject AS C

      subject = tInbox.subject
      body = tInbox.body
      ? body

      Comment


        #4
        Re: email automation addrecord script

        Your script will not work as nRecno needs to be set to a value (a valid number).

        Emails by default go into the a_email.dbf table in the program directory but you can copy it to the app directory and point your email to it there via the email settings.

        If the emails sent and received are html format then the body field will be blank and the body_html field will contain the message.

        Look at the default form view of the table and move thru the records - you will then see whether the data is in the body or body_html field for the particular record number of interest.

        It is a long time since I looked at the email automation stuff but I seem to recall that the samples make the process look far more complicated than it actually is. I found it much better to just manipulate the data in the a_email table and as emails are processed to modify the record to move the email from the Inbox to the Processed "folder" (this is the field name) or whatever folder name you choose.

        Comment


          #5
          Re: email automation addrecord script

          Gary,
          Thank you. I will keep at it. There is not much in the wiki or the help on email automation. It seems it was at the time a direction Alpha was headed in but it hasn't changed much since it was added.

          The code could be better commented and a little deeper explanation of the process would be helpful. There's not much on the message board either.

          There is also an add_record() function in the script that I can not find listed in the help.

          *for_each(x, add_record(t, x), body )

          One question. Is the inbox an object like a form that is pulling its values from the a_email table? If not what is it? A file?

          Tks

          Comment


            #6
            Re: email automation addrecord script

            From memory, add_record() is a custom function contained within that script (down the bottom). As I said, I think the examples are not that helpful.
            In reality the steps are:
            1. Setup email
            2. Have a script fire from time to time that:
            - collects email - see email_receive(), which means emails are automatically added so no need for add_record()
            - query a_email table for new emails that require processing as yes, in answer to your question as I understand it, the inbox is an object like a form that is pulling its values from the a_email table. To see this, copy a_email into your application folder then open the table in the table editor
            - process email and I then modified the record folder (a fieldname) from "Inbox" to "Processed" to prevent re-processing.

            I hope this helps.
            Last edited by Garry Flanigan; 12-30-2010, 05:47 PM. Reason: clarification

            Comment

            Working...
            X