4 Replies Latest reply: May 15, 2014 9:58 AM by lklinstra _ RSS

    Extra long variable length vertical fields

    lklinstra _

      In version 6, it was possible to take a variable vertical length field, that exceeded 254 bytes, parse it into individual lines driving off

      of the ch(10) and ch(13) and put it back together into an area that could hold up to 4096 bytes.

       

      Can this be done some other way with version 8?  We want to create one field to hold the line that starts with 123456789, it can be up to

      about 10 lines.  We want to create another field to hold the error messages which can be one to many.

       

      Here is our report example, the formating is not exact, the variable vertical fields are indented on the actual report, but hopefully this is a good example.

       

      We appreciate your time in looking into this issue.

       

       

      1REPORT NUMBER:  X09999                 NSCC FUND/SERV CONSOLIDATED DEALER ERROR REPORT           PAGE:          24

      SOURCE PROGRAM: X09999                                        REJECTS                                                    SUPER SHEET DATE:  10/03/2005

      JOB:            XXXXX999                                    REGISTRATN                                                                 CURRENT DATE:  10/04/2005

                                                                                      TIME:    02:09:21

        MGMT CODE/NME: XX/ SOME FUND COMPANY                                                                               

      DEST CODE:                                                                               

      FIRM NBR:     188                                                                               

      DEALER NBR/NME:   56283/ SOME DEALER                                                                               

      FUND CODE/NME:     999/ SOME KIND OF FUND                                                                           

      -            NSCC CONTROL NBR: XXXXXXXXXXXXXXX   FUND:     999  ACCT:  9999999999                                                   

                   -


      --1----2+3+4+5+6+7+8+9+--0                   

      123456789   0101B  0188   4000 5586   0077956H815025018852760016919    10032005        0    0                                      

                   9202                 SOME DEALER       7827961111          20188  0470533629                                        

      ERROR                                                                               

      0            PRENIGHTLY REJECT  : X09999 - REJECT ERROR   020 NSCC REJ CODE 020                                                                               

      CUSTOMER ACCOUNT NUMBER AT FIRM MISSING                                                                               

      EXISTING ACCOUNT NOT FOUND                                                                        

      0            PRENIGHTLY REJECT  : X09999 - REJECT ERROR   020 NSCC REJ CODE 020                                                                               

      CUSTOMER ACCOUNT NUMBER AT FIRM MISSING                                                                               

      EXISTING ACCOUNT NOT FOUND                                                                        

      0            PRENIGHTLY WARNING : XXXX9999 - WARNING ERROR 361 - RECORD PROCESSED  -                                                                               

      SUBSEQUENT PURCHASE RECEIVED WITH INVALID ACCT NBR                                                                               

      ACCOUNT-NUMBER-FIRM = 7827961111                                                                               

      ACCOUNT-NUMBER-FUND =                                                                             

      0            PRENIGHTLY WARNING : XXXX9999 - WARNING ERROR 361 - RECORD PROCESSED  -                                                                               

      SUBSEQUENT PURCHASE RECEIVED WITH INVALID ACCT NBR                                                                               

      ACCOUNT-NUMBER-FIRM = 7827961111                                                                               

      ACCOUNT-NUMBER-FUND =                                                                             

      0               NIGHTLY WARNING : WARNING INVALID ACCOUNT NUMBER ENTERED                                                          

      0               NIGHTLY WARNING : WARNING INVALID ACCOUNT NUMBER ENTERED         

                                                        

      1REPORT NUMBER:  X09999                 NSCC FUND/SERV CONSOLIDATED DEALER ERROR REPORT          PAGE:          25

      SOURCE PROGRAM: X09999                                        REJECTS                                                  SUPER SHEET DATE:  10/03/2005

      JOB:            XXXXX999                                    REDEMPTION                                                              CURRENT DATE:  10/04/2005

                                                                                      TIME:    02:09:21

        MGMT CODE/NME: XX/ SOME FUND COMPANY                                                                               

      DEST CODE:                                                                               

      FIRM NBR:     201                                                                               

      DEALER NBR/NME:   56342/ SOME OTHER DEALER                                                                               

      FUND CODE/NME:      99/ SOME OTHER KIND OF FUND                                                                               

      -            NSCC CONTROL NBR: XXXXXXXXXXXXXXX   FUND:      99  ACCT:   999999999                                                   

                   -


      --1----2+3+4+5+6+7+8+9+--0                   

      123456789   0101B  0201   0010 5586   00779556109025020152760087846 30310032005100320051    0                                      

                   0202   0000000091911047755849            2                    0    321144606                                           

                   0303   0000000000000000USD100420050370     0  NOOITGEDAGT  SUSAN  043089544710NY                   0                   

                   0404                        00         0US00000000000000000000        0                                                

                   9505   W668     DOE  JOHN                          00100000000000000000000000000                                      

      ERROR                                                                               

      0               NIGHTLY REJECT  : REDEMPTION SHARES EXCEED UNISSUED                                                                               

      POTENTIAL INSUFFICIENT FUNDS                                                                               

      PAYMENT CODE INVALID FOR NON DCSC FUND                                                                               

      NOT ENTIRE ACCOUNT AND SHARES EQUAL MASTER

        • Extra long variable length vertical fields
          Grant Perkins

          A quick response for now.

           

          I think, if I read your requirements correctly, that you made use of a feature which actually only existed in the 6.02 release and crept in by stealth! It crept out agin at Version 7 ...

           

          In the meantime if you define your multiline field capture as a MEMO field you should be able to capture up to around 65k characters in the field and, in V8, you can perform 'calculations' on the field which result in other memo fields.

           

          One of the calculation types might be to split the lines out of the revised format of the memo field using the TEXTLINE function.

           

          I am not entirely sure if this answer covers all of your needs (or indeed any of them!) but it may be useful. If you already have looked at the Memo fields and TEXTLINE functions then let us know where they fail to satisfy your needs and we can have another go at an alternative approach. As I said earlier - I'm not confident I have fully identified the problems you face.

           

          Have fun.

           

          Grant

           

            Originally posted by lklinstra:

          [font="courier"]1REPORT NUMBER:  X09999                 NSCC FUND/SERV CONSOLIDATED DEALER ERROR REPORT           PAGE:          24

          SOURCE PROGRAM: X09999                                        REJECTS                                                    SUPER SHEET DATE:  10/03/2005

          JOB:            XXXXX999                                    REGISTRATN                                                                 CURRENT DATE:  10/04/2005

                                                                                          TIME:    02:09:21

            MGMT CODE/NME: XX/ SOME FUND COMPANY                                                                               

          DEST CODE:                                                                               

          FIRM NBR:     188                                                                               

          DEALER NBR/NME:   56283/ SOME DEALER                                                                               

          FUND CODE/NME:     999/ SOME KIND OF FUND                                                                           

          -            NSCC CONTROL NBR: XXXXXXXXXXXXXXX   FUND:     999  ACCT:  9999999999                                                   

                       -


          --1----2+3+4+5+6+7+8+9+--0                   

          123456789   0101B  0188   4000 5586   0077956H815025018852760016919    10032005        0    0                                      

                       9202                 SOME DEALER       7827961111          20188  0470533629                                        

          ERROR                                                                               

          0            PRENIGHTLY REJECT  : X09999 - REJECT ERROR   020 NSCC REJ CODE 020                                                                               

          CUSTOMER ACCOUNT NUMBER AT FIRM MISSING                                                                               

          EXISTING ACCOUNT NOT FOUND                                                                        

          0            PRENIGHTLY REJECT  : X09999 - REJECT ERROR   020 NSCC REJ CODE 020                                                                               

          CUSTOMER ACCOUNT NUMBER AT FIRM MISSING                                                                               

          EXISTING ACCOUNT NOT FOUND                                                                        

          0            PRENIGHTLY WARNING : XXXX9999 - WARNING ERROR 361 - RECORD PROCESSED  -                                                                               

          SUBSEQUENT PURCHASE RECEIVED WITH INVALID ACCT NBR                                                                               

          ACCOUNT-NUMBER-FIRM = 7827961111                                                                               

          ACCOUNT-NUMBER-FUND =                                                                             

          0            PRENIGHTLY WARNING : XXXX9999 - WARNING ERROR 361 - RECORD PROCESSED  -                                                                               

          SUBSEQUENT PURCHASE RECEIVED WITH INVALID ACCT NBR                                                                               

          ACCOUNT-NUMBER-FIRM = 7827961111                                                                               

          ACCOUNT-NUMBER-FUND =                                                                             

          0               NIGHTLY WARNING : WARNING INVALID ACCOUNT NUMBER ENTERED                                                          

          0               NIGHTLY WARNING : WARNING INVALID ACCOUNT NUMBER ENTERED         

                                                            

          1REPORT NUMBER:  X09999                 NSCC FUND/SERV CONSOLIDATED DEALER ERROR REPORT          PAGE:          25

          SOURCE PROGRAM: X09999                                        REJECTS                                                  SUPER SHEET DATE:  10/03/2005

          JOB:            XXXXX999                                    REDEMPTION                                                              CURRENT DATE:  10/04/2005

                                                                                          TIME:    02:09:21

            MGMT CODE/NME: XX/ SOME FUND COMPANY                                                                               

          DEST CODE:                                                                               

          FIRM NBR:     201                                                                               

          DEALER NBR/NME:   56342/ SOME OTHER DEALER                                                                               

          FUND CODE/NME:      99/ SOME OTHER KIND OF FUND                                                                               

          -            NSCC CONTROL NBR: XXXXXXXXXXXXXXX   FUND:      99  ACCT:   999999999                                                   

                       -


          --1----2+3+4+5+6+7+8+9+--0                   

          123456789   0101B  0201   0010 5586   00779556109025020152760087846 30310032005100320051    0                                      

                       0202   0000000091911047755849            2                    0    321144606                                           

                       0303   0000000000000000USD100420050370     0  NOOITGEDAGT  SUSAN  043089544710NY                   0                   

                       0404                        00         0US00000000000000000000        0                                                

                       9505   W668     DOE  JOHN                          00100000000000000000000000000                                      

          ERROR                                                                               

          0               NIGHTLY REJECT  : REDEMPTION SHARES EXCEED UNISSUED                                                                               

          POTENTIAL INSUFFICIENT FUNDS                                                                               

          PAYMENT CODE INVALID FOR NON DCSC FUND                                                                               

          NOT ENTIRE ACCOUNT AND SHARES EQUAL MASTER /font[/quote][/b][/quote]

           

          [size="1"][ November 03, 2005, 10:19 AM: Message edited by: Grant Perkins ][/size]

          • Extra long variable length vertical fields
            lklinstra _

            Thanks for the reply.  You also helped me more accurately display my report sample.  I'm kind of new to this.  We had been working with this report in version 7 for a while, not getting the results we wanted.  We got help from someone in another part of the company who had the solution, but only with the Monarch version 6.02 you referred to, but we were not able to replicate his results with our different version.  We are considering an upgrade to version 8 specifially for this feature, so I don't currently have the version 8 TEXTLINE feature to experiment with yet.  I'm going to try to find my way around the website to read more about that feature.  Thanks for your reply.  Laura

            • Extra long variable length vertical fields
              Grant Perkins

              Hi Laura,

               

              I created a file using your sample post cau and pasted into Wordpad and then saved as a .txt file and on that basis I can confirm that V8 and the TEXTLINE function will successfully separate the lines back out of the multiline memo field.

               

              I think it was actually 6.01 that had the interesting text handling feature (looking back at a discussion in topic 99 on the forum) but that doesn't help you much.

               

              If I get a chance later I will see what can be done in V7 BUT if you have the opportunity to go to V8 anyway I would really recommend it because it will surely be easier to do what I understand you need to do and has the benefit of the PDF file reading capability as well.

               

               

              Grant

               

               

              UPDATE:

               

              Definitely go for V8 if you can!

               

              Using V7 it looks like it would be possible (in the absence of anything on the report that could act as an end of line 'flag') to assume that a longish string of spaces (about 15 I think) probably represents the end of a line (you can make the field long enough to force this) and you could therefore substitute a different character for the string of spaces. This would give you marker for a line break and you could then use a function like LSPLIT to break the line in 2.

               

              Up to the marker is your first line.

               

              To get the second line you run a formula against the second part of the previous process which does the same thing again - in effect each time removing the first part of the string of characters for a length that corresponds to the line as it was originally.

               

              Not nice and it may require some careful work with formulae to make it happen but it looks like it could be done.

               

              The downside is that you need to define enough calculated fields, using this method repetitively, to provide a field for each of the maximum number of fields that you may ever come across. Whilst duplicating the calculated fields is not so bad, knowing how many you need might not be so easy if the number of lines could be quite variable. And in most cases it will likely leave you with a lot of empty fields in the data table.

               

              The bad news is that even in V8 you need to know how many fields you are likely to need to cope with the largest record. But at least the TEXTLINE function makes the formula much easier to work with.

               

              If you normally have a reasonably controlled number of lines but occasionally need several more it might be possible to come up with a way of dealing with the anomalous records by flagging them up as potential problems rather than carry a data table with many redundant fields for most records.

               

              I can expand on this description of you end up stuck without a V8 upgrade but to be honest the V7 approach would look clumsy compared to V8 so I would prefer not cause any confusion if it can be avoided!

               

              Let us know if you need to do something before the V8 solution is in place.

               

              [size="1"][ November 05, 2005, 06:14 AM: Message edited by: Grant Perkins ][/size]

              • Extra long variable length vertical fields
                lklinstra _

                Thanks, I think my manager is pretty sold on the upgrade.  We want to make the best use of our time, so it sounds like version 8 will be what we need.  Part of our limitation is the way this works with some other internal software that does not like variable memo fields.  That is why we need to use calculated fields to split up the data from the memo field into more definitive parts.  It is believed that the TEXTLINE function will give us the needed solution.  I'll have a chance to see how it works when we get installed.  Thanks for your feedback.