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

Turning calc fields "on" or "off&qu

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

    Turning calc fields "on" or "off&qu

    I just got a tip from the man, himself...Selwyn, but am not sure how to do what he suggested. He responded to my last question on Numeric Value Out Of Range. He said I could turn the calculated fields "on" or "off"...I responded with the question of how to do this - and spent the last 1/2 hour looking through HELP...but I think he's on to bigger and more challenging questions, by now.

    Anyone know how to turn calcs on and off?
    Thanks,
    Wanda

    #2
    RE: Turning calc fields

    Easy.
    In field rules, in the first tab "Field types", change any "Calculated" field to "User entered".

    Jake

    Comment


      #3
      RE: Turning calc fields

      Doing so also deletes the calculation, which means I'd have to re-write it and re-evaluate the field rules every time I want to add or change a record. This seems much more cumbersome than what Alpha is usually capable of. Any other ideas?

      Comment


        #4
        RE: Turning calc fields

        Of course you could create a text file or a spreadsheet and store your field rules to be cut and pasted as necessary.
        There can be only one.

        Comment


          #5
          RE: Turning calc fields

          Great idea - I'll tuck that one under my belt. Your solution of writing the calc field this way, however, works just fine and is less cumbersome:
          if(exit_date>DOB,(EXIT_DATE-DOB)/365,0

          Thank you for your help, Stan!
          Wanda

          Comment


            #6
            RE: Turning calc fields

            Wanda,
            I've noticed one think you might want to keep in mind. If you change a "calculated" field to "user entered", the calculation is still retained by A5. If you shortly turn the field back to "calculated", the expression will sometimes magically reappear. If you compact the database, however, I think A5 deep-sixes old info, and the expression is gone. You really can't turn calculated fields on and off at will in field rules, like you are thinking. Selwyn just meant to remove the calculations, then put them back one at a time to see which one doesn't work, then fix the expression like Stan did for you so the calculation works correctly.

            Comment


              #7
              RE: Turning calc fields

              Makes perfect sense to me :-) Sometimes I can get too literal. Thanks for the explanation.

              I've left calculations alone when changing to User Entered, assuming they'd be deleted once User Enter was checked. And I ran into some problems, so assumed that leaving the calculation there in the background was what was causing the problem. Don't remember right now what the problem was. So I re-checked Calculated field, deleted the calculation (yes, it was still there in this case), and the problem went away. May have been a fluke.
              Thanks,
              Wanda

              Comment

              Working...
              X