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

Reminder System Strategy

  • Filter
  • Time
  • Show
Clear All
new posts

    Reminder System Strategy

    I would like to add a reminder system to my application. I have scoured the documentation and Message Board for references and I have not found any. I have found many discussions on building and integrating to calendar applications including a nice add-in by Jerry B. But these don't seem to meet my need of incorporating an Outlook style reminder system into A5. So I am starting this thread in hope of generating some dialogue on the development of an A5 based reminder system.

    Here are my current requirements for the system:

    * Multi-User Support - system would distinguish between reminders set up by different users in a multi-user application.
    * Once a reminder is created and scheduled for a future date and time the reminder system will pop-up a window on top of ALL OTHER open windows displaying the reminder and allowing the user to dismiss it, snooze it or reschedule it.

    Those are the very basic needs. Most of this seems straight forward. Script_Schedule() could be used to trigger the pop-up of reminders and XDialogue could be used to deal with the pop-ups. However the part of this that is most intriguing and important to me (at least) is efficiently triggering the reminders. Here are some possible strategies:

    * Schedule a script to run every 5 minutes that would query a table of reminders for reminders that belong to the current user and pop-up a window for any that appear in the next 5 minutes. This seems really inefficient to me and would generate a lot of overhead and network traffic.
    * As each reminder is added schedule one of the ten script_schedule() timers. This seems pretty efficient. There would need to be a script that would pre-load the timers when the application initially loaded and also some really interesting script work that would manage the timers as new reminders were added, dismissed, snoozed and rescheduled.

    I sure hope this elicits some suggestions from the community as I could use some ideas!


    Re: Reminder System Strategy

    some suggestions from the community as I could use some ideas!
    Use one of a multitude of free reminder, PIM, etc applications available.
    There can be only one.


      Re: Reminder System Strategy

      Hi Stan,

      Thank you for your reply. I guess to stimulate suggestions that are appropriate to my need I need to enumerate some additional requirements:

      * There is a prospect master table in this application and all reminders are to tie back to a prospect that is in this table.
      * This application operates in a multi-user environment. There are managers that review the work of the salespeople. They need to be able to see all of the reminders that a given salesperson has created.
      * Salespeople don't always work at the same workstation. A reminder system that does not store data on the local station is important and can move transparently with the user is a requirement.
      * The prospecting system allows a salesperson to take over the leads of another salesperson when they are sick or on vacation. Once again this requires that the reminder system's data be accessible via the network.

      Without just flat out specifying that the system is to be implemented in Alpha Five I am attempting to layout a set of specifications that makes it evident that this is the direction that needs to be taken.

      Once again I thank anyone who takes the time to share their suggestions on this topic.



        Re: Reminder System Strategy

        There is nothing that I can see in your specs that can't be done in A5. But it is a little complicated. I guess it might be better if you ask a specific question for a specific problem, rather than throw out such a broad inquiry. My suggestion would be to do it one step at a time w. Qs asked one at a time accordingly.
        AlphaBase Solutions, LLC

        [email protected]


          Re: Reminder System Strategy

          I've done a close version of what you're describing - it's not difficult, and overhead is minimal. I know someone else has too - I just don't remember who.

          For the two systems where I do it (same customer - just two databases) a Main Menu is always running. The Main Menu has a timer set for every 60 seconds. We just that to check a variety of flags and conditions.

          Use something like the exist() function to check for a flag or condition, and then as necessary do the other stuff to build the message for the interface.

          You'll be surprised at how easy this is.


            Re: Reminder System Strategy

            Hi Steve,

            Thank you for the suggestion on the timer event on the Main Menu. I always leave the Main Menu open in the application so this could be a very useful tool. I will explore this option.

            It is suggestions like these that are just little golden nuggets when trying to build a specification for a new project.