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

Suggestions appreciated

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

    Suggestions appreciated

    Given:
    Child table containing from 0 to 100 records identified by a prefix (AAA,AAB etc.) and a sequence # (1-100)
    Required:
    To create a single record for each prefix (AAA,AAB etc.)for printing in a fixed format determined by the sequence #. Have created a table with 100 fields corresponding to the sequence #. How can I fill this table ?

    Any suggestions would be appreciated,
    John

    #2
    RE: Suggestions appreciated

    You will have to write an xbasic script that increments your values & addresses the field names. Hopefully you named the fields something like Sequence001, Sequence002... & Prefix001, Prefix002..., etc. You can use a for/next loop along with the eval function to address the field names. A little tricky to do, but not to outrageous.
    Peter
    AlphaBase Solutions, LLC

    [email protected]
    https://www.alphabasesolutions.com


    Comment


      #3
      RE: Suggestions appreciated

      Peter
      Thanks for the reply. I am x-basic challenged as in NO x-basic. Is there any other way ? If not I quess I will wait for the conference to learn.
      Thanks, John

      Comment


        #4
        RE: Suggestions appreciated

        John,

        I'm confused. Do you want a single record for each prefix, or do you want each prefix to be in a single field?

        Why 100 fields?

        -- tom

        Comment


          #5
          RE: Suggestions appreciated

          john:

          for the file with the prefix field add another field Seqno, numeric, 3, 0(Name, type, length, decimal positions)
          use update operation and assign a serial number to the Seqno field. increment by one.

          I hope this helps.

          bob adler

          Comment


            #6
            RE: Suggestions appreciated

            If you have already built the table with 100 records with sequence #'s 1-100, couldn't you set the first prefix to "AAA" then make it an auto increment field? I was trying to test, but got bogged down.I wanted to see if it would go to AAB, AAC, AAD...to AAZ. I wanted to see what the next incremet would be. I was hoping it would go to ABA.

            Comment


              #7
              RE: Suggestions appreciated

              Tom
              I need 1 record per prefix, (AAA,AAB etc. ONLY if the prefix is in the child table), which contains 100 fields which = the sequence numbers in the child table (by Prefix). The child table may contain 1 to 100 records per prefix. My report will print the 100 fields on a single page, filling in the fields (data) by sequence #,s where present. eg.

              AAA (Seq-08)
              AAA-01-VG (Seq 10.4) AAA-02-VG (Seq 26.4) ...
              AAA-01-VB (Seq-10.5) AAA-05VB (Seq 26.5) ...
              AAA-01 (Seq 11) data AAA-27 (Seq 27) ..
              AAA-02 (Seq 12) AAA-28 (Seq 28) ...
              AAA-03 (Seq 13) AAA-28 (Seq 29) ...
              AAA-04 (Seq 14) data AAA-28 (Seq 30) ...

              AAA-02-VB (Seq-14.5)data AAA-06VB (Seq 30.5) ...
              AAA-05 (Seq 15) AAA-29 (Seq 31) ... etc.

              Essentially I wish to create 1 page per prefix IF so much as 1 child record is present. The fact that many fields may be blank is as important as being filled. The blanks indicate future possible changes. Thanks for your reply, hope this clears up the confusion.
              John



              Comment


                #8
                RE: Suggestions appreciated

                Sorry previou post not spaced properly, will try again.
                Tom
                I need 1 record per prefix, (AAA,AAB etc. ONLY if the prefix is in the child table), which contains 100 fields which = the sequence numbers in the child table (by Prefix). The child table may contain 1 to 100 records per prefix. My report will print the 100 fields on a single page, filling in the fields (data) by sequence #,s where present. eg.

                .....................AAA (Seq-08)
                AAA-01-VG..(Seq 10.4)........... AAA-02-VG.(Seq 26.4) ...
                .AAA-01-VB.(Seq-10.5)............ AAA-05VB.(Seq 26.5) ...
                ..AAA-01...(Seq 11).data.......... AAA-27..(Seq 27) ..
                ..AAA-02...(Seq 12)............... AAA-28..(Seq 28) ...
                ..AAA-03...(Seq 13)............... AAA-28..(Seq 29) ...
                ..AAA-04...(Seq 14).data.......... AAA-28 (Seq 30) ...
                .
                .AAA-02-VB.(Seq-14.5).data...... AAA-06VB (Seq 30.5) ...
                ..AAA-05...(Seq 15)...............AAA-29 (Seq 31) ... etc.
                .
                Essentially I wish to create 1 page per prefix IF so much as 1 child record is present. The fact that many fields may be blank is as important as being filled. The blanks indicate future possible changes. Thanks for your reply, hope this clears up the confusion.
                John

                Comment


                  #9
                  RE: Suggestions appreciated

                  Thomas
                  Unfortunately the prefix cannot be predetermined and must be taken from the child file (if present). It may start at AAD skip to BBC etc.
                  See my post to Tom Clone moments ago for a detailed explaination.
                  Thanks
                  John

                  Comment


                    #10
                    RE: Suggestions appreciated

                    Robert
                    The file does contain a sequence #. I will try your suggestion of an update operation. Hopefully I overlooked the SIMPLE solution.
                    Thanks muchos
                    John

                    Comment


                      #11
                      RE: Suggestions appreciated

                      John,

                      I'm sorry, but I still don't get it.

                      On the one hand it's clear each record will have a single three letter prefix, determined from an existing field in the table.

                      On another, it's clear each record will appear in order based on the value of a sequence code in each record. This needs to be concatenated with the prefix to assure correct order in the report.

                      What remains a mystery is why 100 fields in each and every record?

                      I apologize for being so dense. Probably used to simpler problems. Definitely more comfortable with actual data samples (field names and values), and line by line examples of what the output should resemble, using the actual data sample for illustration.

                      Can you give us an example of what two source records would look like, and then show us how you want them to appear on the report?

                      -- tom

                      Comment


                        #12
                        RE: Suggestions appreciated

                        Tom
                        I know your not dense. Must be my lack of a clear definition, so let my try again.

                        Input table DHI (Simplified)

                        REC#....DHI..........SEQ_NO.....LOCATION

                        001.....AAA...........7.0.......Finance
                        002.....AAA-01-VG....10.4.......Accounting
                        003.....AAA-01-VB....10.5.......A/R
                        004.....AAA-01.......11.0.......Billing
                        005.....AAA-02.......12.0.......Credit
                        ......no further records with AAA PREFIX
                        006.....AAC-52.......62.0.......Sales
                        ......no further records with AAC PREFIX
                        .
                        Required O/P (table then report). One record per prefix showing all 100 fields with LOCATION (If child record exists)or blank (If no child record exists).
                        .
                        REC#.PREF.....FIELD #...DHI...........LOCATION
                        001..AAA......SEQ_01....GMK(Constant) "ALL"
                        ..............SEQ_02....blank.........blank
                        ..............SEQ_03....A.(CALC)......blank
                        ..............SEQ_04....blank.........blank
                        ..............SEQ_05....AA.(CALC).....blank
                        ..............SEQ_06....blank.........blank
                        ..............SEQ_07....AAA.(PREFIX)..Finance
                        ..............SEQ_10.4..AAA-01-VG.....Accounting
                        ..............SEQ_10.5..AAA-01-VB.....A/R
                        ..............SEQ_11....AAA-01........Billing
                        ..............SEQ_12....AAA-02........Credit
                        ..............SEQ_13 to SEQ_99........blank
                        002..AAC......SEQ_01 to 06 as AAA
                        ..............SEQ_07....AAC...........blank
                        ..............SEQ_08 to SEQ_61........blank
                        ..............SEQ_62....AA-52.........Sales

                        Hope this clarifies & not further confuses.

                        John

                        Comment


                          #13
                          RE: Suggestions appreciated

                          Tom Cloned?

                          The mind boggles ... expontially increased help from Tom? Would that we were so fortunate!

                          Couldn't help it, Frisay night/Saturday morning humor.

                          Finian
                          Finian

                          Comment


                            #14
                            RE: Suggestions appreciated

                            John, thanks. That helped a lot.

                            Two more quick questions:

                            1) in the output sample for record# 1, did you leave out the sequences for SEQ_08 and SEQ_09 on purpose or by accident?

                            2) If some of the sequence numbers have 2 significant digits and some have 3, don't you need to populate 1000 possible fields, instead of just 100? i.e. in the output sample for record#1, do the values for SEQ_10.4 and SEQ_10.5 go in fields 10 and 11? If so, where do the values for SEQ_11 belong?

                            -- tom

                            Comment


                              #15
                              RE: Suggestions appreciated

                              John, instead of 1000 in the previous post, substitute 999 (three digits)... haven't had my coffee yet this AM!

                              -- tom

                              Comment

                              Working...
                              X