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

Popup.Calendar

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

    Popup.Calendar

    Apparently The popup calendar will not return a date to a date field. If you use a character field for a date field you cannot then use date arithmetic. I was wondering if a calendar can be assigned to a button without returning any value to a field? Just a popup calendar for user convenience..

    #2
    Re: Popup.Calendar

    Originally posted by KarlS View Post
    Apparently The popup calendar will not return a date to a date field. If you use a character field for a date field you cannot then use date arithmetic. I was wondering if a calendar can be assigned to a button without returning any value to a field? Just a popup calendar for user convenience..
    The documentation doesn't suggest that assigning the result to anything is required. Have you tried a button with the code

    popup.calendar(dtoc(date()))
    There can be only one.

    Comment


      #3
      Re: Popup.Calendar

      Stan,

      I have been trying to figure out what the code argument is for returning a date value to a date field from the popup calendar function attached to a button. Rather than putting a button on the date header in an imbedded browse (causes the browse header to get fat and ugly), I would like to put a hotspot on the area so when the user clicks on it the popup calendar appears and the selected date is returned to the date field. Do you have that code or know where I can find it?

      The code for assigning the F11 key is what I use now but it isn't very intuitive for the user unless you provide a label instruction which is cludgy to the user interface. I believe the correct way to handle it is by assigning the right code to a hotspot. Thanks.

      Regards,
      Gordon

      Comment


        #4
        Re: Popup.Calendar

        Date_String as C = POPUP.CALENDAR( Default_Date_String as C )
        Date_Value as D = CTOD( Formatted_Date as C )
        So CTOD(POPUP.CALENDAR( Default_Date_String as C ))

        yields a date.

        Is that the question?
        There can be only one.

        Comment


          #5
          Re: Popup.Calendar

          Thanks Stan,

          No, it didn't do what I needed but the following did exactly what I wanted. This script will pop the selected calendar date into whatever date field has the focus. It only seems to work with the hotspot object tool. The button object tool causes the selected date field to lose the focus and the date doesn't drop into the field. Using a hotspot object also requires the use of an underlying static text object in order to give the hotspot form and appearance... otherwise you don't see the hotspot. I bold the text, give the text object background color, some drop shadow, and small rounded corners so that it appears to be a button. The secret is to make sure the invisible hotspot lies in front of the text object in order to function.

          sDate=popup.calendar ("Enter Date",dtoc(date()))
          a_user.key.handled = .T.
          sys_send_keys(sDate)

          The following will give you the calculator and drop the calculated value in whatever numeric field has the focus.

          sNum=popup.calculator (0)
          a_user.key.handled = .T.
          sys_send_keys(sNum)

          The way to do this is save these scripts and then call them by name with another script. This way they are available anywhere you need to call them with a hotspot/text button, utilising the onpush event.

          I was just so tired yesterday I just couldn't extract these lines from some other code listed on this site.

          Regards,
          Gordon

          Comment

          Working...
          X