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

Calculated field defaults to zero

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

    Calculated field defaults to zero

    I have a calculated field that does a simple field1 - field2 numerical calc. I've noticed that the calculated field defaults to zero when adding a new record. This is despite the initial value being set to Null in A5 and to nothing in my Access Db. I've also tried setting the default value in Access to Null but to no avail.

    If I remove the calculation from the field the default value is null, so it certainly appears that by having a calculation defined I get a zero.

    Does anyone know how to avoid showing zero in a calculated field.

    Regards, Richard.

    #2
    Re: Calculated field defaults to zero

    Change your calculated field to use a custom function like result_of(field1,field2) then in the javascript functions define a function
    like
    Code:
    function result_of(field1,field2){
    	if(field1-field2 != 0 && field1-field2 != null){
    		var c = field1-field2;
    		return c;
    	}else{
    		return '';
    	}
    }
    Or, if you choose, you can do it all in the calculated field:
    Code:
    if(field1-field2 = 0,'',field1-field2)
    Jim Coltz
    Alpha Custom Database Solutions, LLC
    A5CustomSolutions.com
    [email protected]

    Comment


      #3
      Re: Calculated field defaults to zero

      Thanks Jim, that's a good idea... although in my case 0 may be a valid result from the calculation so I would want to show the result as 0 if field 1 and field 2 aren't null and the result is 0. It's a simple mod of your example to do this so thanks.

      Another idea I came up with is to use a show/hide expression - to hide the calculated field and then display it when field1 and field2 aren't empty.

      Regards, Richard.

      Comment


        #4
        Re: Calculated field defaults to zero

        Another idea is to put this :

        alltrim(str( convert_type(<value>,"N") ,250,2,"B")) - 2 decimals

        alltrim(str( convert_type(<value>,"N") ,250,0,"B")) - NO decimals

        in DISPLAY FORMAT in the DISPLAY SETTINGS on the CALCULATED FIELD.

        Basically, it means displaying any number with 2 decimals and NOTHING if the number is 0.

        Mike.Blank if zero.jpg

        Comment


          #5
          Re: Calculated field defaults to zero

          This is ugly, but I think it does what you want.
          I assume a dialog with 3 numeric fields, and a button to initiate the check.

          Code:
          if({dialog.Object}.getValue('FIELD1')=='' ||{dialog.Object}.getValue('FIELD2')==''){
          
          {dialog.Object}.setValue('FLDRESULT','' );
          alert('you have a null value, no math will be performed');
          }
          else{{dialog.Object}.setValue('FLDRESULT',{dialog.Object}.getValue('FIELD1')-{dialog.Object}.getValue('FIELD2'))}
          Gregg
          https://paiza.io is a great site to test and share sql code

          Comment


            #6
            Re: Calculated field defaults to zero

            If you want to make sure only numbers are processed, this code is better:

            Code:
            if(isNaN({dialog.Object}.getValue('FIELD1'))||{dialog.Object}.getValue('FIELD1')==''||isNaN({dialog.Object}.getValue('FIELD2'))||{dialog.Object}.getValue('FIELD2')=='')
            {{dialog.Object}.setValue('FLDRESULT','' );
            alert('something is NaN');}
            else{{dialog.Object}.setValue('FLDRESULT',{dialog.Object}.getValue('FIELD1')-{dialog.Object}.getValue('FIELD2'))}
            Gregg
            https://paiza.io is a great site to test and share sql code

            Comment

            Working...
            X