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

Problem with Memo field

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

  • Problem with Memo field

    Using version 4.5 build 266 on a 14-user Windows NT Server/NT Workstation network: We recently started using a Memo field very heavily (notes of ongoing customer information). Once in a while, some text seems to duplicate itself from one customer file to another customer file. The Memo field is on a tabbed subform. Any ideas/suggestions/clues?

    Thanks.
    Jay

  • #2
    RE: Problem with Memo field

    Jay,

    Try a search on this board for memo fields. There have been some issues discussed and your's might be one of them.

    kenn
    TYVM :) kenn

    Knowing what you can achieve will not become reality until you imagine and explore.

    Comment


    • #3
      RE: Problem with Memo field

      Kenn,
      Thanks for the lead. It appears to be a genuine "problem" that I will have to work around. Fixed in Version 5 ?

      Jay

      Comment


      • #4
        RE: Problem with Memo field

        Hi Jay,

        Yes, that is my understanding. Like you, I use memofields, especially the Rich Text. Every day that goes by is one day closer to A5's release.

        kenn
        TYVM :) kenn

        Knowing what you can achieve will not become reality until you imagine and explore.

        Comment


        • #5
          RE: Problem with Memo field

          Jay, at the Alpha Five conference last November Dr. Wayne gave a talk describing things he does to improve his applications. He dealt with memo fields at some length. If I recall correctly, his design prevents the user from spending lots of time crafting the initial memo record before it is saved. Instead, when the user 'enters' a new memo, the memo is saved immediately, and then reopened for user edits. To the user it's invisible. However, by doing it this way he assures a good link between the pending memo record and the related tables, even in a multi-user setting. He also designs the input process so that the user cannot leave the memo field to work on other aspects of the current transaction without either cancelling or saving the memo itself. (Hope I remembered this correctly!)

          Comment


          • #6
            RE: Problem with Memo field

            I've also read that some people do not include their memo fields in the main table the set is based upon, but rather a seperate table linked one-to-one to the main table. I believe that Ira Perlow is a proponent of this. Try searchin for "Ira Memo", you may find his suggestions on this.
            Thank you,
            Mike Konoff

            Comment


            • #7
              RE: Problem with Memo field

              I am using 4.03 the following code my do what you are asking. I have 2 forms one with a button which causes the second form to open with the appropriate link to the first form, line feed, add a date and then place cursor at end of text. Lynn Morey and Bob Adler helped me with this.

              ' repairitem is the form
              ' problems is the button object on form
              ' memoform is the form with the problems and repairs memo fields

              DIM MEMOLINK AS C
              ' get the current value of the linking field from parent form
              ' opens memotable and checks if link is present.If not present
              ' in table then add new record in memotable with current link

              ':REPAIRITEM:LINK.ACTIVATE()
              MEMOLINK =LINK.VALUE
              TBL=TABLE.OPEN("MEMOTABLE.DBF")
              IF .NOT.EXIST(MEMOLINK,"MEMOTABLE.DBF","LINK") THEN

              TBL.ENTER_BEGIN()
              MEMOTABLE->LINK=MEMOLINK
              TBL.ENTER_END()
              TBL.CLOSE()
              END IF

              ' opens memoform at problem field

              FORM.VIEW("[email protected]")
              :MEMOFORM.ACTIVATE()


              ' check to see if the form is in change mode
              TBL =TABLE.CURRENT()

              :MEMOFORM.INDEX_SET("LINK")
              :MEMOFORM.FIND(MEMOLINK)


              TBL.CHANGE_BEGIN()

              ' memotable is the table name
              ' problem is the memo field in memotable
              ' take the existing problem and add line feed and carriage return to seperate the previous problem
              ' then add date and then the next line is set
              :MEMOFORM:PROBLEM.ACTIVATE()


              :MEMOFORM:PROBLEM.VALUE=:MEMOFORM:PROBLEM.VALUE +chr(13)+chr(10)+" "+mdy(date())+" - "+upper(totime(toseconds(time()),11,0))+": "


              TBL.CHANGE_END()


              :MEMOFORM.INDEX_SET("LINK")
              :MEMOFORM.FIND(MEMOLINK)
              :MEMOFORM:PROBLEM.ACTIVATE()

              SYS_SEND_KEYS("{CTRL-END}")

              Comment

              Working...
              X