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

Help adding to a memo field

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

    Help adding to a memo field

    I want to add text to a memo field that may already have text in it. So far my way of doing this (code below) works fine except for one thing: If in the xdialog one puts in a blank line, as in 2 paragraphs of text, that one line between paragraphs turns into 3 blank lines in the text added to the memo field, which of course is undesirable.

    Perhaps there is some other way to do this? I want the newest entry added to the top of the memo field, not appended to the end, and only one line between paragraphs.

    Ray

    Code:
    dim New_text as c
New_text = ""
result=ui_dlg_box("New Conversation Log Entry",<<%dlg%
{region}
{wrap=60}
In the Log your message will be time stamped and you will have the option of e-mailing it.;
You can add blank lines with the Enter key.;
[%MW%.60,10New_text];
{endregion};
{region}
<*15Save> <15Cancel>
{endregion}
%dlg% )

If result = "Save"
    parentform:conv_log.field.readonly =.f.
    dim t_conv as p
    dim D_T_stamp as c
    D_T_stamp = time("M/d/y "+v_user_initials+"h:0mAM:  ",now())
    t_conv = table.current(5)
    'If the memo already has text, add a crlf() to new_text and
    'put in date/time stamp from above in either case.
    IF len(trim(t_conv.conv_log)) > 0
        parentform:conv_log.Activate()
        sys_send_keys( D_T_stamp+new_text+crlf())
    else
        parentform:conv_log.Activate()
        sys_send_keys(New_text)
    end if
    xbasic_wait_for_idle()
    parentform:conv_log.field.readonly =.t.
else
    end
end if
end

    Tags: None
    #2
    Re: Help adding to a memo field

    Originally posted by Raymond Lyons View Post
    I want to add text to a memo field that may already have text in it. So far my way of doing this (code below) works fine except for one thing: If in the xdialog one puts in a blank line, as in 2 paragraphs of text, that one line between paragraphs turns into 3 blank lines in the text added to the memo field, which of course is undesirable.

    Perhaps there is some other way to do this? I want the newest entry added to the top of the memo field, not appended to the end, and only one line between paragraphs.

    Ray
    Hi Ray,

    I'm doing something similar. I'm appending to the end of the memo field and using a crlf() if there is already a comment present. I went ahead and altered my code to put the latest comment first and it seems to work without the problem you are seeing.

    The code that puts the latest comment first follows.

    Code:
    initials = ui_get_text("Initials (Required)","Enter your initials","","lll") 'Get users initials into variable with mask for 3 letters only.
if initials = "" then
    ui_msg_box("Error","Initials are required to make changes.")
    end
end if

DIM SHARED comm as C = ""
DIM SHARED varC_result as C = ""
heading_string = "Patient will NOT see this comment."
ok_button_label = "&OK"
cancel_button_label = "&Cancel"
varC_result = ui_dlg_box("Enter Reason for Void",<<%dlg%
{region}
{text=95,1:heading_string};
{endregion};
{region}
| [%mw%.80,10comm];
{endregion};
{line=1,0};
{region}
<*15=ok_button_label!OK> <15=cancel_button_label!CANCEL>
{endregion};
%dlg%)

if comm = "" then
    ui_msg_box("Error","You must supply a reason for voiding this invoice.")
    end
end if

initials = format_data(initials,"C") 'change initials to all uppercase to look better!

if topparent:comment.value<>"" then
		topparent:comment.value=comm+"--"+initials+"--"+date()+crlf() +comment.value 
		else
		topparent:Comment.value = comm+"--"+initials+"--"+date()
end if
    Jim Coltz
    Alpha Custom Database Solutions, LLC
    A5CustomSolutions.com
    [email protected]

    Comment

      #3
      Re: Help adding to a memo field

      Originally posted by Jim Coltz View Post
      Code:
      ...

if topparent:comment.value<>"" then
        topparent:comment.value=comm+"--"+initials+"--"+date()+crlf() +comment.value 
        else
        topparent:Comment.value = comm+"--"+initials+"--"+date()
end if
      Jim,

      Thanks! Except that I want "crlf(2)" where you have just 1 added line, this solves the 3 line issue. Kind of wish I understood why my previous method threw in 2 extra blank lines (it does not if you just display it in a message box) but hey, as long as I have something that works, I'm happy!

      Ray

      Comment

        #4
        Re: Help adding to a memo field

        When i try this i get a type mismatch error. Indeed i am trying to take a character fields & append them to a memo field.
        My problem code is listed below
        I have tested each variable to be sure they all contain the correct data.
        thanks for any suggestions - old tony
        Code:
        if :Lead_EntryEM:field19.value<>"" then
    :Lead_EntryEM:field19.value = "Email with Subject of "+ Lead_EntryEM.EMSubject.value + " from " + Lead_EntryEM.EMFrom.value + " was sent " + date() +crlf()+ field19.value
    else
    :Lead_EntryEM:field19.value = "Email with Subject of "+ Lead_EntryEM.EMSubject.value + " from " + Lead_EntryEM.EMFrom.value + " was sent " + date() +crlf()
end if

        Comment

          #5
          Re: Help adding to a memo field

          Date() returns a date field. You need this as a string. Use dtoc(date()).

          Ray

          Comment

            #6
            Re: Help adding to a memo field

            Originally posted by oldtony View Post
            When i try this i get a type mismatch error. Indeed i am trying to take a character fields & append them to a memo field.
            My problem code is listed below
            I have tested each variable to be sure they all contain the correct data.
            thanks for any suggestions - old tony
            Code:
            if :Lead_EntryEM:field19.value<>"" then
    :Lead_EntryEM:field19.value = "Email with Subject of "+ Lead_EntryEM.EMSubject.value + " from " + Lead_EntryEM.EMFrom.value + " was sent " + date() +crlf()+ field19.value
    else
    :Lead_EntryEM:field19.value = "Email with Subject of "+ Lead_EntryEM.EMSubject.value + " from " + Lead_EntryEM.EMFrom.value + " was sent " + date() +crlf()
end if
            Raymond has given you the solution. You can fancify it with some of the date format options available to dtoc() like

            dtoc(date(),"8") yields "March 23rd, 2007"
            There can be only one.

            Comment

              #7
              Re: Help adding to a memo field

              I would of thought that automatic typecasting would have taken care of the conversion.

              From the interactive window

              Code:
              t = "test " + date() + " Date" 
?t
= "test 03/24/2007 Date"

?typeof(t)
= "C"
              Jim Coltz
              Alpha Custom Database Solutions, LLC
              A5CustomSolutions.com
              [email protected]

              Comment

                #8
                Re: Help adding to a memo field

                This is why I basically don't trust anything "automatic" like that. Too much chance that it will either slow things down (usually only an issue in a loop) or not work in some situations. An extra second or so to type ctod(date()) rather than just date() is worth it to me.

                It's nice that Alpha tries to make things easier but it can also lull people out of good habits or, worse yet, they may never figure out how it would be done "normally" in case they need it or in case they switch to another program that doesn't have that automatic feature.

                Comment

                  #9
                  Re: Help adding to a memo field

                  Originally posted by CALocklin View Post
                  ... An extra second or so to type ctod(date()) rather than just date() is worth it to me.
                  Maybe dtoc(date()) would work even better. ;)

                  Comment

                    #10
                    Re: Help adding to a memo field

                    Just wanted to know if anybody was paying attention!:)

                    Comment

                    Previous template Next
                    Working...
                    X