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
Devcon 2020 Goes Virtual! LEARN MORE >

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

Dated Memo Entries

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Dated Memo Entries

    In the Code Archive there is a sample of a script to assign a date stamp in front of all entries into the memo field.

    It works great except the carriage return issue. After one entry the next entry starts right after the last character of the previous entry. I've seen many different ways to script CR's on this board and none of them seem to work for me.

    Here's his script just for review:

    '--- ACTIVATE THE MEMO FIELD
    Parentform:Status.Activate()

    '--- GET TEXT STRINGS FOR THE MONTH, DAY, AND YEAR.
    mno = substr( cdate( date()), 5, 2 )
    dno = substr( cdate( date()), 7, 2 )
    yno = substr( cdate( date()), 3, 2 )

    '--- CREATE THE 'DATE' TEXT STRING
    '--- NOTE THAT IT ENDS IN A COLON AND 2 SPACES
    date_text = mno + "-" + dno + "-" + yno + ": "

    tc = table.current()
    '--- IF THE MEMO ALREADY HAS SOME TEXT, GO TO THE END
    '--- AND ADD A NEW LINE.
    IF len(trim( tc.status )) 0
    sys_send_keys( "{LEFT}" )
    sys_send_keys( "{^END}" )
    sys_send_keys( chr(13) )
    END IF

    '--- ENTER THE DATE TEXT
    sys_send_keys( date_text )

    END

    Could there be a typo somewhere or spaces where there shouldn't be (or vice versa)?

    Anyone who sees anything please advise.
    Tags: None
    #2
    RE: Dated Memo Entries

    I'd add

    sys_send_keys( chr(13) )
    sys_send_keys( chr(10) )

    right before the END statement

    You may want to repeat them to provide a blank line...

    Comment

      #3
      RE: Dated Memo Entries

      So this is interesting,

      Doing what you suggested I get the CR I want but only AFTER the date has printed (so the date is still right up against the last entry).

      Does it have to do with that IF statement? Not sure why the key "left" is there, I understand Ctrl-End. Any other ideas?

      Thanks!

      Jane

      Comment

        #4
        RE: Dated Memo Entries

        Jane, if you want blank lines anywhere in the memo, just insert the two lines I gave you.

        So, for example, if you want a blank line before the date,
        insert them before the line which reads:

        '--- ENTER THE DATE TEXT

        Comment

          #5
          RE: Dated Memo Entries

          Well I can only assume I've done something wrong in the copying and pasting because those command lines work fine before the END statement but nowhere else. I've tried multiples, changing the 10s and the 13s, etc.

          I will continue to ponder...

          Comment

          Previous template Next
          Working...
          X