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

>= Nano Trivia <= , or is it?

  • Filter
  • Time
  • Show
Clear All
new posts

    Re: &gt;= Nano Trivia &lt;= , or is it?

    Originally posted by rleunis View Post
    You stated: "The point of my question is the implementation of the combined operands ">=" and "<="."

    So I thought you did not like combined operands...

    That's why I gave you an alternative solution...
    Not that I don't like "Combined" operands, it's the redundency of it. At what point somebody's brain says I will look for anything "more than" L vs I will look for anything "More than or equal to" M?
    Originally posted by rleunis View Post
    The restriction of an integer of 1 was not part of the original post, I think...
    The thread is not all about ">=" when it comes to numerics only nor there are restrictions to integers only. That part was only in response to the example in your post. I already spent plenty enough time stating, use the value immediately before the one you are testing for. Doesn't have to be integer, but some brave soul ventured into infinity which took this discussion on a big detour that didn't have to happen as infinity has no place here.
    I am not sure if I am speaking Greek? Which part of this people are having trouble understanding?
    At what point your brain decides that you've got to use ">=" while you could simply and have many times used ">"? Just for simplicity 's sake, answer this question for me if you can:
    What compels someone to say >=M instead of >L?
    Can you answer that? Do you have to use .not.<M?
    Originally posted by rleunis View Post
    Anyway it does not change my post and validity of it, I think.
    No.. I am sorry because now you are back in the same arena as ">=" where alpha has to do the double check:
    You might as well stick with ">=".
    Last edited by G Gabriel; 10-24-2009, 02:23 PM.


      Re: &gt;= Nano Trivia &lt;= , or is it?

      "What compels someone to say >=M instead of >L?
      Can you answer that? Do you have to use .not.<M?
      Real live example:
      Suppose you are looking for a partner.
      And one of the criteria is:
      He or she is at least as big as me?
      You are referencing your own height, so you would be looking for a partner which is equal or greater than you.
      Or you would be looking for someone not smaller than yourself.
      I suppose you would not be looking for someone greater than yourself minus 1 (or what ever other increment)...
      would you?
      It's all about what are you referencing to.


        Re: &gt;= Nano Trivia &lt;= , or is it?

        What compels someone to say >=M instead of >L?
        Simple. When the possibility exists that a value being tested will be less than M but greater than L ... and you don't want anything less than M.


          Re: &gt;= Nano Trivia &lt;= , or is it?

          >= is essential when evaluating a date. If a user is required to enter a 'date from' and then 'date to', you must use >= to if the 'date to' includes the 'date from' in its equation as a valid date. This is releavant to most calander type activities based on days or time. A days sick leave can be entered as 'from today' - 'to today' giving a value of 1 day off sick.

          You will always need to reflect on input of at least two dates, the only way that make this > only is to change the way a user operates and actually thinks about dates and time. Using the arguments in this thread, the user would need to enter >yesterday in the 'date from' and <tomorrow in the 'date to', to achieve a value of today. Illogical thought process to most