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 calculation confusion

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

  • Date calculation confusion

    My client complained that she is constantly forgetting to check indexes, and would like a reminder to check if she has not done so for 30 days.

    I have written a small piece of code (OK, converted Action Script to Xbasic) to do this, but cannot get it to work.

    I have a configuration table containing a field called Indexcheckdate that stores the date the indexes were last checked (Type = Date). When the code runs, this date is retrieved and stored in a variable called "indexdate". The date should then be checked against today's date to see if 30 days have passed. If not, no action should be taken.

    The dialog box always displays, even when the value of indexdate variable is less than 30 days before today's date (verified by text in dialog box). I am guessing there is something wrong with the line "IF a5_eval_expression("=(date()- Var->indexdate > 30)") THEN ", but I don't know what.

    Code:
    DIM indexdate AS D
    'get date indexes last checked
    tbl = table.open("configuration")
    indexdate = tbl.Indexcheckdate
    tbl.close()
    'Check if 30 days have passed since indexes were last checked
    IF a5_eval_expression("=(date()- Var->indexdate > 30)") THEN 
    'Displays a message box.
    DIM   indexreminder_result as N
    DIM   indexreminder_YES_Button as L 
    DIM   indexreminder_NO_Button as L 
    indexreminder_YES_Button = .F.
    indexreminder_NO_Button = .F.
    
    title_var = "Check Indexes"
    'Message is an expression. Need to evaluate the expression in the context of the current form.
    message_text_var = a5_eval_expression("=\"You have not checked the table indexes for 30 days.\"+chr(13)+chr(10)+\"Would you like to check them now?\"+chr(13)+chr(10)+chr(13)+chr(10)+\"Indexes last checked on \" + Var->indexdate",local_variables())
    indexreminder_result=ui_msg_box(title_var,message_text_var,UI_YES_NO+ UI_FIRST_BUTTON_DEFAULT+ UI_ATTENTION_SYMBOL)
    'Test to see which button on the message box was pressed....
    SELECT
    	CASE indexreminder_result = UI_YES_SELECTED
    		indexreminder_YES_Button= .t.
    	CASE indexreminder_result = UI_NO_SELECTED
    		indexreminder_NO_Button= .t.
    END SELECT
    END IF
    
    'If user clicks on "Yes" button
    IF indexreminder_YES_Button THEN 
    a5_CheckIndexesDialog(controlpanel.Active())
    'Update indexcheckdate to today's date
    dim tbl as P
    tbl = table.open("configuration")
    tbl.change_begin()
    tbl.Indexcheckdate = date()
    tbl.change_end(.T.)
    tbl.close()
    
    END IF
    If computers are so clever how come someone as dumb as me has to tell them what to do?

  • #2
    Re: Date calculation confusion

    I've never understood the utility of a5_eval_expression().

    Code:
    indexdate = {09/01/2012}
    
    
    ? a5_eval_expression("=(date()- Var->indexdate > 30)") 
    = "=(date()- Var->indexdate > 30)"
    
    ? date()- Var->indexdate > 30
    = .F.
    So just change

    IF a5_eval_expression("=(date()- Var->indexdate > 30)") THEN
    to
    IF date()- Var->indexdate > 30 THEN
    There can be only one.

    Comment


    • #3
      Re: Date calculation confusion

      I have tried that but get an error message that the "Indexreminder_Yes_button" is not found. So it is still trying to display the message box, but not dimensioning the array for dialog buttons (presumably because less than 30 days between dates).
      Alphagrab.jpg
      If computers are so clever how come someone as dumb as me has to tell them what to do?

      Comment


      • #4
        Re: Date calculation confusion

        I didn't design the logic flow. You test the button pushed after your first if loop but the variable is only defined and set inside that loop. So if the date doesn't fall in the needing checking range, you still test it.

        Code:
        DIM indexdate AS D
        'get date indexes last checked
        tbl = table.open("configuration")
        indexdate = tbl.Indexcheckdate
        tbl.close()
        'Set up variables so they can be used in either loop
        DIM   indexreminder_result as N
        DIM   indexreminder_YES_Button as L 
        DIM   indexreminder_NO_Button as L 
        indexreminder_YES_Button = .F.
        indexreminder_NO_Button = .F.
        'Check if 30 days have passed since indexes were last checked
        IF date()- Var->indexdate > 30 THEN 
        'Displays a message box.
        title_var = "Check Indexes"
        'Message is an expression. Need to evaluate the expression in the context of the current form.
        message_text_var = a5_eval_expression("=\"You have not checked the table indexes for 30 days.\"+chr(13)+chr(10)+\"Would you like to check them now?\"+chr(13)+chr(10)+chr(13)+chr(10)+\"Indexes last checked on \" + Var->indexdate",local_variables())
        indexreminder_result=ui_msg_box(title_var,message_text_var,UI_YES_NO+ UI_FIRST_BUTTON_DEFAULT+ UI_ATTENTION_SYMBOL)
        'Test to see which button on the message box was pressed....
        SELECT
        	CASE indexreminder_result = UI_YES_SELECTED
        		indexreminder_YES_Button= .t.
        	CASE indexreminder_result = UI_NO_SELECTED
        		indexreminder_NO_Button= .t.
        END SELECT
        END IF
        
        'If user clicks on "Yes" button
        IF indexreminder_YES_Button THEN 
        a5_CheckIndexesDialog(controlpanel.Active())
        'Update indexcheckdate to today's date
        dim tbl as P
        tbl = table.open("configuration")
        tbl.change_begin()
        tbl.Indexcheckdate = date()
        tbl.change_end(.T.)
        tbl.close()
        else
        ui_msg_box("OK","Indexes are fairly current!",UI_OK)
        END IF
        There can be only one.

        Comment


        • #5
          Re: Date calculation confusion

          Thanks Stan.

          That did it.
          If computers are so clever how come someone as dumb as me has to tell them what to do?

          Comment


          • #6
            Re: Date calculation confusion

            Debug(1) is our friend.

            If you insert that line in the first modification of your script you will see that the date()- Var->indexdate > 30 was false so the flow jumped past everything in that loop and the next executed line was IF indexreminder_YES_Button THEN. But since that variable was never initialized by the loop, you received an error.
            There can be only one.

            Comment

            Working...
            X