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

emailing a transaction list/history

  • Filter
  • Time
  • Show
Clear All
new posts

  • emailing a transaction list/history

    I am just getting to grips with A5's internal email functions, and getting some realy useful resuls (one of the best bew features)

    I have a typical one to many db set up, what I would like to do is put the transactions associated with the current parent record in an e-mail.

    I know I can e-mail the contents of a memo field.
    Is it possible to build a routine that goes through the current records associated transactions, and append them to a memo field on the parent record so I can send them in an e-mail?

    I have a couple of ideas, but is there an elegant way of doing this?

    Many thanks
    Chris Tanti
    Technical Support

    Nuance & Fathom Ltd - The data-driven marketing agency

  • #2
    RE: emailing a transaction list/history

    this feature is now built into a5v5.

    see the release notes for the patches.

    when you create the email message, click the "insert command" button, then select the One to Many command (command will only be there if your form is based on a set with one-many links.

    the command will insert this into your email (this example is for alphasport's invoice set)

    put any fields you want from the transaction table into the region between the start and the end of the one-many command.


    Replace this text with field from the table.



    • #3
      RE: emailing a transaction list/history

      That sounds much simpler than what I came up with over the weekend!

      I wanted to hard code the email into a button and not use A5's internal mail, is that possible with your method.

      My example is below.



      tbl.email_note = ""

      WHILE .not. child_tbl.fetch_eof()
      xline="("+str(count)+") "+dtoc(tbl_mail_trans->date_mailed)+" Units:"+ \
      str(tbl_mail_trans->units_mailed)+" "+trim(tbl_mail_trans->posting_type)+ \
      " "+trim(tbl_mail_trans->outer_used)

      tbl.email_note = xprevline

      var->xclientfullname=ltrim(trim(people->title)+" "+trim(people->first_name)+" "+trim(people->last_name)+" "+trim(people->suffix))

      dim e as p
      e =
      e.send_subject="R&M Posting Alert For Job "+ltrim(str(tbl_job->job_number))
      e.send_contents="Ref Job: "+ltrim(str(tbl_job->job_number))+chr(10)+"This is am alert to inform you that *** has mailed the following items"+chr(10)+chr(10)+tbl_mail_header->email_note
      if e.errors "" then
      end if
      delete e

      xstatus=" Post info emailed"
      Chris Tanti
      Technical Support

      Nuance & Fathom Ltd - The data-driven marketing agency


      • #4
        RE: emailing a transaction list/history

        you can do it your way but it is hard.

        the easiest way is to

        1. define your template.
        2. use the action script genie to "send an e-mail message"
        3. choose the a5 internal client.
        4. the a5 internal client gives you the option of just sending the email WITHOUT opening the client.

        no need to do any programming here at all.