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



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

Sending Email Best Practices - What are they?

  • Filter
  • Time
  • Show
Clear All
new posts

  • peteconway
    Yes - Thanks Steve it was very helpful.

    Leave a comment:

  • Steve Workings
    A couple years ago at Alpha Devcon, Pete Conway asked me for info on how to implement this. I made a video for him, and I think a file/sample package. My method works with A5 runtime, and uses the timer on a runtime form to trigger the process every 60 seconds.

    I know I still have the video - just checked to verify that. So if you want the video -- and if I can find it any file/code examples -- send me an email at [email protected]

    Leave a comment:

  • kiwibruce
    Originally posted by Steve Workings View Post
    A work queue and runtime processor for that is highly recommended.

    Selwyn's example when the work queue was first released was about the email delay. We've implemented a work queue, processed by a separate runtime instance. The runtime processes work queue records every 60 seconds. We've added much more to that over the years including long-running reports.
    Hi Steve,
    I have never looked at the workQueue before but it could really be powerful,
    I watched all of Selwyn's videos. The missing bit for me is it ends with him showing the Work queue record with the xbasic Script in the field... How do create a process to run that xbasic?

    Thanks Bruce

    Leave a comment:

  • RustyB
    Yes I have used Runtime before. Perhaps I can just schedule it to run on Logon of the server. Then my Work Queue processor can just sleep for a minute if there is no work to do. Not sure if there is any downside to this continuous loop method as opposed to simply running the task every few minutes and then exiting.

    Leave a comment:

  • mikeallenbrown
    I use Windows Task Scheduler to run a bat file how ever often I need. The bat file runs a command line string that initiates and runs a script in Alpha runtime. I think your first step is to (if you don't already have it) buy a runtime license. I don't know how much that is. You'd have to talk to Alpha sales.

    Leave a comment:

  • RustyB
    This work queue is intriguing to me. Reading up on it, it seems that Alpha basically provides you the ability to add tasks to a Work Queue, but leaves the developer in charge of actually processing it. Alpha recommends possibly using an Xbasic script (or other process) that does the work specified and then possibly sleeps for a minute and then checks for more work. Sounds simple enough. My question (forgive me if this is obvious) is what actually kicks off the worker queue? How do I ensure it is always running? I can manually start it, but if the server is ever restarted, do I have to manually remember to start it every time. What is the best practice for this? I am using IIS Server and Alpha build 6488 if that is helpful. Thanks.

    Leave a comment:

  • mikeallenbrown
    Thanks Steve. I've found this Work Queue in the documentation. I'll read up on it.

    Leave a comment:

  • Steve Workings
    A work queue and runtime processor for that is highly recommended.

    Selwyn's example when the work queue was first released was about the email delay. We've implemented a work queue, processed by a separate runtime instance. The runtime processes work queue records every 60 seconds. We've added much more to that over the years including long-running reports.

    Leave a comment:

  • Sending Email Best Practices - What are they?

    Web app running 6488 (standard app server).

    Within my app are a variety of automatic emails (and some manual). Currently I'm using Alpha to send these emails: email_send_noprofile(). This works fine, but, there is a pause that the user experiences as Alpha connects to the email server, sends the email, and waits for a response back. It's this pause I want to avoid. I'm imagining many users sending or initiating an automatic email within my app and the app server instance gets bogged down.

    I've recently started to have the Microsoft SQL database handle my automatic emails through triggers using: msdb.dbo.sp_send_dbmail. This works well too but I am wondering if my SQL DB is sending a lot of emails if that would slow down the responsiveness of the DB. Anyone know?

    There is also the option of building my email system in runtime and initiating that as needed. Often times the user wants to email a file that was already uploaded to AWS S3 so the pause in Alpha is even longer. I'm leaning towards making all my automatic emails send through the DB and the manual emails sent through a custom runtime routine.

    I'd like to hear other developers thoughts on this. Thank you.