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 and Time Stamp button for memo field

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

  • Date and Time Stamp button for memo field

    Some months ago, I posted a script I used to enter the current date and time in a memo field of a contact manager application. You can follow all the different ideas posted in the thread by using the Search feature of this Message Board and putting "automatic date entry into memo field" in the search window.

    I have since noted a "A5 freezing and crashing" problem using this script that only occurs in records that have many lines (e.g. 35 lines) of conversation notes in the memo/note field. The same button, with the same script, works perfectly fine in the same application, as long as there not a bunch of lines (approx. 35 or more) already filling the memo field.

    If you research the previous thread noted above, the procedure in the past was to, in effect, copy the existing notes in the memo field and place the date and time at the beginning or top of the memo field. Basically a "copy and paste" concept. There apparently must be a "memory limit" as to how large a chunk of existing data (notes) can be stored in my previous script procedure as I was recently started having A5 freeze on me when I pressed the "Date and Time Stamp" button; only in records with a large chunk on existing notes.

    I have since modified the button script as I found that I could manually enter the date and time in these same records with large amount of existing notes (35 lines +). Thus, I didn't think it was a problem with how much info can be stored in a memo field, but the (copy/paste/add the current date and time) script itself was the culprit.

    Below is my current Date and Time Stamp button script, which basically uses a bunch of sys_send_keys to duplicate manually typing in the date and time. It works great. It's pretty simple and direct. I'm always open to hear of suggestions. I post this script because I know others use A5 for contact management and a Date/Time Stamp notation to a memo/notes field is important and handy.

    ''XBasic

    'Puts the Date and Time Stamp at TOP = BEGINNING of memo field

    'The following is the button script to put the date and time
    'in a memo field
    'This time stamps each new entry of a new conversation
    'This form is used as a contact manager

    'Definitions follow
    ':BUYMORE is the form name
    'NOTES is the object name of the memo field

    'This line brings focus to the notes memo field
    :Buymore:NOTES.activate()

    'The following lines push existing text down and return the
    'cursor to the top left corner of the memo field
    sys_send_keys("{Enter}")
    sys_send_keys("{Enter}")
    sys_send_keys("{UP}")
    sys_send_keys("{UP}")

    'The next line probably will wrap on this Board.
    'This sys_send_keys line needs to be on one line.
    sys_send_keys(" "+MDY(date())+" - "+upper(totime(toseconds(time()),11,0))+": ")


    'The line above now sets you up with
    'the cursor now at the right end of the
    'top line of the memo field
    'two spaces to the right of the current date and time
    'ready for typing new conversation notes ENJOY

  • #2
    RE: Date and Time Stamp button for memo field

    Additional note. It appears the sys_send_keys line with the MDY in it that I was concerned might get wrapped on this Board, was NOT wrapped. That's good so as to not add any confusion.

    Just a little further explanation to the script.

    'MDY displays the date for example as April 24, 2000
    'the multiple parenthesis places the date in
    '12 hour AM PM mode
    'There are other variations of displaying the time format
    'See the Xbasic manual for TOTIME with table on page 480
    'This format display like this
    ' September 23, 2001 - 9:45 PM:

    Comment


    • #3
      RE: Date and Time Stamp button for memo field

      I use the following in field rules as default for a memo field; it could easily be modified with a time value.

      if(isblank("memo-field"),"Added on "+mdy(date()),memo-field)

      Comment


      • #4
        RE: Date and Time Stamp button for memo field

        Thomas,

        Thanks for your post to the Alpha Message Board. I found some time and I've been trying to experiment with your suggestion. Where do you put that default line for the memo field in the field rules? When I go to the data
        entry tab of the field rules of a memo field, virtually all options are grayed out. The "default" line where I thought this line would be placed is available in other field types, but not for a memo field.

        I must be missing something. Your thoughts are appreciated.

        Thanks,
        Lynn

        Comment

        Working...
        X