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

Memo Field Issue

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

    #46
    Re: Memo Field Issue

    I believe Tom has correctly identified the record without issues there.
    Instead, I believe, the 2nd open record is reading the wrong (same name) variable to be written.
    Tom is one of the really sharp guys here and probably has enough information now to figure out what the real problem is and get it corrected.

    He almost always posts back what he found, so we should all be able to learn.
    Dave Mason
    [email protected]
    Skype is dave.mason46

    Comment


      #47
      Re: Memo Field Issue

      Please Google issues for dbase memo fields or search this message board for more info.
      Al Buchholz
      Bookwood Systems, LTD
      Weekly QReportBuilder Webinars Thursday 1 pm CST

      Occam's Razor - KISS
      Normalize till it hurts - De-normalize till it works.
      Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
      When we triage a problem it is much easier to read sample systems than to read a mind.
      "Make it as simple as possible, but not simpler."
      Albert Einstein

      http://www.iadn.com/images/media/iadn_member.png

      Comment


        #48
        Re: Memo Field Issue

        dave
        I never doubted tom's ability, my comments were only regarding the implicit reference to the record. should one get the record explicitly getting via table.fetcth method or ambiguous table.get method. I would second your comment on tom's ability at any time.

        in my tests, the table.get() did not fare well, but table.fetch_find() worked better.
        Last edited by GGandhi; 05-31-2015, 06:59 AM.
        thanks for reading

        gandhi

        version 11 3381 - 4096
        mysql backend
        http://www.alphawebprogramming.blogspot.com
        [email protected]
        Skype:[email protected]
        1 914 924 5171

        Comment


          #49
          Re: Memo Field Issue

          Originally posted by Al Buchholz View Post
          Please Google issues for dbase memo fields or search this message board for more info.
          I am assuming you are telling me this, since dave is an experienced programmer it is not directed at him, I am sure.
          I did look it up in case you are telling me. my friend peter's article is widely quoted in this forum and google was not any help at all.

          as per peter
          table navigation should be prevented during editing and only to be allowed on read only conditions.
          memo field to be edited using the form that does not allow navigation.
          seems his statement and mine are the same to prevent any corruption of memo fields.

          it is the same article stan pointed out earlier in the thread.
          Last edited by GGandhi; 05-31-2015, 07:01 AM.
          thanks for reading

          gandhi

          version 11 3381 - 4096
          mysql backend
          http://www.alphawebprogramming.blogspot.com
          [email protected]
          Skype:[email protected]
          1 914 924 5171

          Comment


            #50
            Re: Memo Field Issue

            Originally posted by GGandhi View Post
            I am assuming you are telling me this, since dave is an experienced programmer it is not directed at him, I am sure.
            I did look it up in case you are telling me. my friend peter's article is widely quoted in this forum and google was not any help at all.

            as per peter
            table navigation should be prevented during editing and only to be allowed on read only conditions.
            memo field to be edited using the form that does not allow navigation.
            seems his statement and mine are the same to prevent any corruption of memo fields.

            it is the same article stan pointed out earlier in the thread.
            This is an problem with dbase that happens with any language that uses dbase tables. I.e. Fox Pro et. al.

            We can minimize the occurrence with techniques of Alpha but it doesn't eliminate them.
            Al Buchholz
            Bookwood Systems, LTD
            Weekly QReportBuilder Webinars Thursday 1 pm CST

            Occam's Razor - KISS
            Normalize till it hurts - De-normalize till it works.
            Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
            When we triage a problem it is much easier to read sample systems than to read a mind.
            "Make it as simple as possible, but not simpler."
            Albert Einstein

            http://www.iadn.com/images/media/iadn_member.png

            Comment


              #51
              Re: Memo Field Issue

              This is getting to be a long thread so I'm not sure if this has been suggested.

              Immediately after

              tbl = table.get("cb_header")

              get the ssn and caseno into local variables.

              Wrap the section writing the notes to the table in an if section that verifies the variables match the record being written to.

              if tbl.ssn_field = ssn_local_variable .and. tbl.caseno_field = caseno_local_variable
              'clear out p_text
              p_text = ""
              'get previous notes and add new notes to them
              p_text=tbl.Notes
              tbl.change_begin()
              tbl.Notes = "*** Case Notes - "+ut(tbl.caseno)+" *** "+c_name+" *** "+ date() + ": " +" ("+wcode+" - " +wname +")" +crlf()+alltrim(sumnotes)+crlf()+"************"+crlf()+p_text
              tbl.change_end(.t.)
              delete sumnotes
              delete p_text
              delete vCase
              Else
              msgbox("Wrong record!")
              end if
              There can be only one.

              Comment


                #52
                Re: Memo Field Issue

                Sorry, guys, I didn't look at this over the weekend.

                We HAD shadows prior to ver 10. With ver 10, Shadowing (at least in my case) becomes very tricky. We administer many different social service programs, each being a separate database called from our main menu database (hence the addin variables) and (rightly or wrongly), we keep their tables in separate folders, or we would have THOUSANDS of tables, indexes, dictionaries all in one folder which would be impossible to keep track of. Our Client Information database needs to have information from at least 5 to 10 "other" databases (ie folders). When it is shadowed, the shadowing routine creates new sub-folders under the shadowed "CASEREG" folder (our Client Information database folder) for each table defined in a different database. When the shadowed database is accessed, we have all sorts of issues with the master tables NOT being in subfolders of the shadowed database. I was able to get around this by manually going in and redefining in the newly shadowed database where the "other" tables actually were. IT is a very tedious process, and with the amount of changes and tweaks we make to the database, it became impractical.

                I will look further into the unique naming of variables.

                Non-shadowed databases load to the local PC's. There is NO processing done on the server. If this wasn't the case, I would need a CRAY liquid nitrogen cooled supercomputer to handle the workload. All our server does is "serve" data and load databases definitions to the local PC's.

                I will also see what I need to do to change from table.get to table.open.

                Thanks, everyone for all your input. It is greatly appreciated for a very frustrating issue.

                Tom

                Comment

                Working...
                X