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

Compare Memo Fields

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

    Compare Memo Fields

    There have been several threads on audit trails and the fact that A5V5 won't/can't compare memo fields. Well it appears the same is true in V6.

    One of my files to be audited has a single memo field which may contain 2000 characters or more and yes, it needs to be audited.

    One of my other files to be audited has 3 memo fields, all of which need to be audited.

    Has anyone found a workable solution for comparing memo fields? Do I have to write the memo field to a text file then do a line by line comparison? Is there a way to compress the field then compare it in compressed format?

    Any help would be appreciated.

    Jerry Gray

    #2
    RE: Compare Memo Fields

    Jerry,

    I'm new to Alpha so I may be wrong. I don't understand what you mean when you say "audited". If I wanted to compare two memo fields in Alpha, I presume that you could place the memo fields into string variables and then compare the strings. If you have to compare one or more against all of the memos, I think an array would be the way to go. Everything in memory would be quicker than reading from your hard drive (if you have the memory).

    Comment


      #3
      RE: Compare Memo Fields

      Al,

      Apparently memo fields are different animals in that they can hold an unlimited amount of information.

      I assume that there are other reasons why they can't be compared or the Alpha Gurus would have added that functionality.

      Hope this makes it more clear and doesn't just muddy the water for you.

      Jerry Gray

      Comment


        #4
        RE: Compare Memo Fields

        Jerry,

        They sure can be compared. I do it all the times. You have to move the contents of the memo field to a blob variable and compare them, but it will work even with binary data. There are other methods as well, all depending on what you want to do. A binary compare is relatively easy.

        Regards,

        Ira
        Regards,

        Ira J. Perlow
        Computer Systems Design


        CSDA A5 Products
        New - Free CSDA DiagInfo - v1.39, 30 Apr 2013
        CSDA Barcode Functions

        CSDA Code Utility
        CSDA Screen Capture


        Comment


          #5
          RE: Compare Memo Fields

          Ira,

          I'm using the basic script from Dr. Peter Wayne's book. I should be able to test for the memo field right after it tests for the STATUS field. If it is the memo field, copy it to the blob, compare and save if necessary and continue. Is this right?

          Thanks for your help,
          Jerry Gray

          Comment


            #6
            RE: Compare Memo Fields

            Ira,

            I have attached my script for my audit trail.

            "FIELD".VALUE_GET()
            "FIELD".INITIAL_VALUE_GET()

            These two functions do not return the same type of data when used against a Memo field (not RTF). I've tried putting the returned value into both a Character and Blob variable. Both generated a "Variable type mismatch" error.

            My script is being played from the Record Events in the Field Rules of my primary file.

            I just need to get both the current and initial values into like formats so I can compare them.

            I am using the latest patch of V6, build: 1536...2011
            Windows XP Pro, SP2 installed (yeah, I know)

            Anyone have any ideas?

            I don't have V5 to test if the results are the same in an earlier version.

            I don't have a lot of hair left to pull out ;")

            Thanks,
            Jerry Gray

            Comment


              #7
              RE: Compare Memo Fields

              For anyone who is trying to use the "FIELD".INITIAL_VALUE_GET() on a memo field!

              Selwyn has informed me that the "FIELD".INITIAL_VALUE_GET() does not work with memo fields. He is checking into it.

              Jerry

              Comment


                #8
                RE: Compare Memo Fields

                Has this been fixed?

                Is there a work around?

                -- t

                Comment


                  #9
                  RE: Compare Memo Fields

                  Tom,

                  I never heard any more on this issue. Selwyn gave me a workaround to get the initials value of the memo field. I am using it for auditing records. Following you will find the code that is placed in the CanEnterRecord and CanChangeRecord events. The second part is an excerpt showing the comparison of the before and after value of the memo field.

                  In the Field Rules for the file
                  Both CanEnterRecord and CanChangeRecord events
                  ------------------------------------------------------------
                  dim shared Memo1_Init_Value as c

                  dim t as p
                  dim f_memo1 as p

                  t = table.current()

                  f_memo1 = t.field_get("Incident_Desc")

                  Memo1_Init_Value = f_memo1.value_get()

                  ------------------------------------------------------------
                  In the Field Rules for the file
                  CanSaveRecord event
                  Run This Script
                  ------------------------------------------------------------

                  dim shared Memo1_Init_Value as c

                  dim tbl as p
                  DIM audit AS P
                  DIM mode AS n

                  DIM i_Incident_Desc AS b

                  DIM c_Incident_Desc AS c

                  tbl=table.current()
                  mode=tbl.mode_get()
                  'mode of 1 is a change, 2 is a new entry ; deleted records on CanDelete field rule

                  audit = table.open("Incident_audit",FILE_RW_SHARED)
                  audit.enter_begin()

                  c_Incident_Desc = tbl.eval("Incident_Desc")

                  dim blank_Date as d

                  if mode=1 then
                  'if the initial value equals the current value, save as blank else save the current value
                  audit.INCIDENT_DESC = if(i_Incident_Desc=c_Incident_Desc," ",c_Incident_Desc)
                  audit.Status="C"

                  elseif mode=2 then

                  audit.Incident_Desc = tbl.eval("Incident_Desc")
                  audit.Status="E"

                  end if
                  audit.enter_end()
                  audit.close()

                  --------------------
                  If this isn't clear, let me know and I will send you a straight email where the indentations help make it easier to read.

                  Hope this helps,
                  Jerry Gray

                  Comment


                    #10
                    RE: Compare Memo Fields

                    Jerry, thanks!

                    -- t

                    Comment


                      #11
                      RE: Compare Memo Fields

                      Tom,

                      Jerry Gray's approach might be a better work around for me. I guess I'm convinced there is a bug in the .initial_value_get() method. Gerard Lynne reported that he was able to get it work with A5V4.

                      Regards,
                      Gary

                      Comment


                        #12
                        RE: Compare Memo Fields

                        Gary,

                        Selwyn did say that it doesn't work with memo fields. What he didn't say was if it was intended to work with memo fields or if will in the future.

                        Later,
                        Jerry Gray

                        Comment


                          #13
                          RE: Compare Memo Fields

                          Tom,

                          I'm just glad I had something to contribute that someone else could use.

                          Jerry Gray

                          Comment


                            #14
                            RE: Compare Memo Fields

                            Jerry,

                            Me, too! :)

                            -- t

                            Comment


                              #15
                              RE: Compare Memo Fields

                              According to the release notes Build 1544-2027 - 19-Nov-2004:

                              "FLD".Initial_value_get() Method - This method now works for Memo fields.


                              Thought you might want to know...

                              Jerry Gray

                              Comment

                              Working...
                              X