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

Days360

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

    #16
    Re: Days360

    David that works :) Now I've moved on to placing into the repeating rows. (great right-up ) I'm using the following. Still works, however, I 'm getting the same valve in each row.
    I'm missing something else. Just to be clear the Billdate and Paid dates are populated via a DBF table's field. Do I all need to change the e_set to 1,2,3?


    function days360 as c (e as p)

    sDate = e.dataSubmitted.Billdate[1]
    sDate = e.dataSubmitted.Billdate[2]
    sDate = e.dataSubmitted.Billdate[3]
    eDate = e.dataSubmitted.Paid[1]
    eDate = e.dataSubmitted.Paid[2]
    eDate = e.dataSubmitted.Paid[3]

    mths = month(ctod(eDate)) - month_number(sDate)

    e._set.Vnomonths.value = mths


    end function

    Comment


      #17
      Re: Days360

      Glad it's working. Have a look at all the comments in the Xbasic function days360. There are a couple of areas about Repeating Sections, as well as some sample code that talks about setting multiple values in Repeating Sections efficiently by generating your own javascript. You can specifically set the each row - it's outlined in the comments. Let me know if it makes sense.

      Comment


        #18
        Re: Days360

        I'm back :)

        As stated this works now that I have correct the date format. However, I am struggling with the repeating sections getting the same data on each row.
        I think the only part missing is the e.dataSubmitted."".size()
        However, I'm getting an error when writing it this way sdate = e.dataSubmitted.billdate.size() Is this not the correct way to state the above?

        function days360 as n (e as p)
        Dim sdate as d

        sDate = e.dataSubmitted.billdate[1]
        sDate = e.dataSubmitted.billdate[2]
        sDate = e.dataSubmitted.billdate[3]


        eDate = e.dataSubmitted.Paid[1]
        eDate = e.dataSubmitted.Paid[2]
        eDate = e.dataSubmitted.Paid[3]


        sdate = date()
        dtoc(sdate,"2/")

        mths = ctod(eDate) - sdate


        e._set.Vnomonths.value = mths

        end function

        Comment


          #19
          Re: Days360

          John,

          Not sure if your calling the Ajax callback from a button on each row, but that's how I set this up.

          Code:
          function days360_detail as c (e as p)
          
          dim rsId as n = e.repeatingSectionInfo.find("CONTAINER_1","ut(name)")
          dim currRow as n = val(e.repeatingSectionInfo[rsId].activeRow)
          dim sDate as c = e.dataSubmitted.BDate[currRow]
          dim eDate as c = e.dataSubmitted.PDate[currRow]	
          
          dim eMth as n = month(ctod(eDate))
          dim sMth as n = month(ctod(sDate))
          mths = eMth - sMth
          
          e._set.NbrMths.value = mths
          
          end function
          I have no idea why the original code I posted used month_number... which converts a month name to a number... so... that's out.

          This looks at the row you're on, grabs the data in that row, does the calc, and puts the result into the dialog.

          Comment


            #20
            Re: Days360

            David this works! I changed it a little to meet my needs. I know get months however, it is displayed as 1.4 as an example.
            I do call this function with a button on each line. Is there another way to call the function once the dialog it retrieved?

            function days360 as c (e as p)

            dim rsId as n = e.repeatingSectionInfo.find("CONTAINER_3","ut(name)")
            dim currRow as n = val(e.repeatingSectionInfo[rsId].activeRow)
            dim sDate as c = e.dataSubmitted.BillDate[currRow]
            dim eDate as c = e.dataSubmitted.paid[currRow]

            dim eMth as d = ctod(eDate)
            dim sMth as d = ctod(sDate)
            mths = EMth - SMth

            e._set.vnomonths.value = mths

            end function


            Thanks for the help.

            Comment


              #21
              Re: Days360

              Hey John,

              You're getting the decimal because the statements that set eMth and sMth are assigned the actual dates, and not just the Month number of that date. The statements should be...

              Code:
              dim eMth as n = month(ctod(eDate))
              dim sMth as n = month(ctod(sDate))
              For doing the calcs when you retrieve data, you can handle this a couple of ways.

              1. Add a field to your database and actually save the months as you calc them. Then, when you retrieve the data, they are in place.
              2. Use the Dialog Client-Side event afterAjaxCallbackComplete. I think this is the best one to use... since you're going to get data, and then calc, this event will fire once the data is in place - because the data retrieval is an Ajax Callback. And, since this event is Client-Side, we get to do the calcs in Javascript...

              Code:
              var cntRows = {dialog.Object}._getRepeatingSectionRowCount('CONTAINER_3');
              var i = 0;
              var begDate;
              var endDate;
              var numBDate;
              var numEDate;
              var mths;
              while (i <= cntRows)
              	{
              	begDate = new Date({dialog.Object}.getValue('BILLDATE:'+i));
              	endDate = new Date({dialog.Object}.getValue('PAID:'+i));
              	numBDate = eval(begDate.getMonth())+1; //uses an offset of 0, so add 1
              	numEDate = eval(endDate.getMonth())+1;
              	mths = numEDate - numBDate;
              	if (isNaN(mths))
              		//in case there are empty rows in the repeating section
              		{}
              	else
              		{
              		{dialog.Object}.setValue('vnomonths:'+i,mths)
              		}
              	i++;
              	}

              Comment

              Working...
              X