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

Date Entering Issues

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

    Date Entering Issues

    Hello, I'm having issues with entering date ranges. When a user trys to enter a date range, popup appears, user starts typing date and popup disappears and cursor advances to next field. Any and all help would be appreciated....

    Below is that code I'm using:

    DIM vcSDate10 as D
    DIM vcEDate10 as D
    DIM vcSEDate10 as N
    DIM varC_result as C
    vcSDate10 = ""
    vcEDate10 = ""
    vcSEDate10 = ""

    ok_button_label = "&OK"
    cancel_button_label = "&Cancel"
    varC_result = ui_dlg_box("Enter Date Range",<<%dlg%
    {region}
    Billing Start Date:| [%DATE;P=popup.calendar(dtoc(vcSDate10));I=popup.calendar%.20vcSDate10!vcSDate10_*];
    Billing End Date:| [%DATE;P=popup.calendar(dtoc(vcEDate10));I=popup.calendar%.20vcEDate10!vcEDate10_*];
    {endregion};
    {line=1,0};
    {region}
    <*15=ok_button_label!OK> <15=cancel_button_label!CANCEL>
    {endregion};
    %dlg%,<<%code%

    if varC_result = "Cancel"
    end
    end if

    if left(a_dlg_button,9) = "vcSDate10_" then
    if a_dlg_button = "vcSDate10_killfocus" then
    vcSDate10 = ctod(dtoc(vcSDate10))
    end if
    a_dlg_button = ""
    end if

    if left(a_dlg_button,9) = "vcEDate10_" then
    if a_dlg_button = "vcEDate10_killfocus" then
    vcEDate10 = ctod(dtoc(vcEDate10))
    end if
    a_dlg_button = ""
    end if
    %code%)

    vcSEDate10 = vcEDate10 - vcSDate10
    parentform:Item_10_Days.value = vcSEDate10
    topparent:Item_10_Rate.activate()

    #2
    Re: Date Entering Issues

    see -- The UI_DLG_NAVIGATE() function moves the cursor and focus to the next or previous control on the Xdialog form.

    Comment


      #3
      Re: Date Entering Issues

      Why manipulate the dates within the dialog? That is more complicated than it needs to be. Get the dates with the dialog and do the math and conversions after the dialog closes.

      Code:
      DIM vd_Sdate as D={}
      dim vd_Edate as D={}
      dim vn_Date10 as N
      DIM varC_result as C
      
      varC_result = ui_dlg_box("Enter Date Range",<<%dlg%
      {region}
      Billing Start Date:| [%DATE;P=popup.calendar(dtoc(vd_SDate));I=popup.calendar%.20vd_SDate];
      Billing End Date:| [%DATE;P=popup.calendar(dtoc(vd_EDate));I=popup.calendar%.20vd_EDate];
      {endregion};
      {line=1,0};
      {region}
      <*15OK> <15CANCEL>
      {endregion};
      %dlg%)
      
      if varC_result = "Cancel"
      	end
      end if
      
      vn_Date10 = vd_EDate - vd_SDate
      msgbox(""+vn_Date10)
      Mike W
      __________________________
      "I rebel in at least small things to express to the world that I have not completely surrendered"

      Comment


        #4
        Re: Date Entering Issues

        Your code has many anomalies (not sure where you got it from? Action Script that you modified?):
        First:
        You dimmed couple variables as D one as N and a another as C
        Code:
        DIM vcSDate10 as D
        DIM vcEDate10 as D
        DIM vcSEDate10 as N
        DIM varC_result as C
        Second:
        You assigned all a value of ""
        Code:
        vcSDate10 = ""
        vcEDate10 = ""
        vcSEDate10 = ""
        Not only you do not need to do so as all variables have a default value of blank (or zero if numeric) but you assigned a character value to a D and N variables.
        Alpha forgave that..but that doesn't excuse it.

        Third:
        In the xdlg code, you have this if statement:
        Code:
        if varC_result = "Cancel"
        end
        end if
        Which is a chicken-egg situation because varC_result is the value of the xdlg itself which will not evaluate until such time that the xdlg is closed therefore having it in the code part of the xdlg defies the laws of gravity.

        Fourth:
        The reason for the behavior you described is simply a counting error:
        In your code, you have:
        Code:
        if left(a_dlg_button,9) = "vcSDate10_" then
        if a_dlg_button = "vcSDate10_killfocus" then
        vcSDate10 = ctod(dtoc(vcSDate10))
        end if
        a_dlg_button = ""
        end if
        This statement will never be true. You should say:
        if left(a_dlg_button,10) = "vcSDate10_" then

        Notice, 10 not 9
        If you make that change, it should work, but you need to take care of the other issues as well

        Comment


          #5
          Re: Date Entering Issues

          ignore
          Mike W
          __________________________
          "I rebel in at least small things to express to the world that I have not completely surrendered"

          Comment


            #6
            Re: Date Entering Issues

            Originally posted by Mike Wilson View Post
            ignore
            We usually do!!
            Tim Kiebert
            Eagle Creek Citrus
            A complex system that does not work is invariably found to have evolved from a simpler system that worked just fine.

            Comment

            Working...
            X