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

parent records only

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

    #16
    RE: parent records only

    Hi Doug,

    I had already done exactly what you said ....... BUT ........ the embedded browse still displays records of every PO.

    Thank you for caring,
    efs

    Comment


      #17
      RE: parent records only

      Hi Phorum,

      OK, here is the latest skinny. I added the display of po_num to the embedded browse temporarily so I could see if it was really getting into the child table, as expected and stated by Tom, it comes in as soon as it is entered in the header. ............. BUT ....... every PO whose alphanumeric value is higher than the value entered, is also displayed !! Any more thoughts?

      efs

      Comment


        #18
        RE: parent records only

        BTW, the set is definitely linked by po_num and ordered on it as well

        efs

        Comment


          #19
          RE: parent records only


          Edward,

          Is is possible that you have the embedded browse based on
          the set rather than the child table linked one-to-many??

          In design mode right click the browse & select properties
          where it says primary table....you should have the name
          of the child table not the name of the set... check it out

          Comment


            #20
            RE: parent records only

            good thawt Doug, but i just checked it, it is on the child table

            Comment


              #21
              RE: parent records only

              Edward,

              How is your set structured....is it just two tables?
              cause ya should only be seeing the child record that
              are related "linked" to the parent based on what you
              are telling me.....I think that your gonna find something
              simple at the bottom of this....or else your tables are
              experiencing some inbreeding... :)

              Comment


                #22
                RE: parent records only

                Hi Doug,

                Thank you for responding, there are just 2 tables in the set. There are 3 other tables in the DB, but they are there only for lookup purposes. You are absolutely right, it will be some small stupid boner

                efs

                Comment


                  #23
                  RE: parent records only

                  EFS,

                  Did you give Tom's suggestion and my instructions a whirl?

                  kenn
                  TYVM :) kenn

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

                  Comment


                    #24
                    RE: parent records only

                    Ed, you should verify that the form is based on the set.

                    You should verify that the link (between the parent table and the child table you want to display in the browse) is based on PO number.

                    You should verify that each child table record (product? item?) has a value in it's PO number field that corresponds to the PO number field in the related parent table record.

                    -- tom

                    Comment


                      #25
                      RE: parent records only

                      Ed, the PO_num must be present in each related pair of records. Once in the parent table record and once in each related child table records. It need not display in the embedded browse. In fact, the default behavior suppresses the link field from the browse's display.

                      The fact that all PO_num records is appearing in your browse suggests that your link definition is defective. Instead of using the PO_num to link the parent and child tables, you're using some value or expression which appears in all child table records... so they all think they're linked to the current parent table record.

                      Make sense?

                      Tell us how you defined the link?

                      -- tom

                      Comment


                        #26
                        RE: parent records only

                        Ed, how about zipping it up and posting it here so we can see it?

                        Feel free to email it to me if privacy is an issue.

                        -- tom

                        Comment


                          #27
                          RE: parent records only

                          Good Morning Ken,

                          I have tried everyones suggestions. Keep in mind that the embedded browse definitely displays the records that it should, but it also displays any record whose alphanumeric value is greater than the chosen one. Furthermore, I have checked and rechecked that the linking and ordering fields are the purchase number field (po_num) of a one to many set with orders_new being the parent and products as the child. There must be a way to filter any po_num greater than the desired value.

                          Thank you all for your suggestions,
                          efs

                          Comment


                            #28
                            RE: parent records only

                            Hi Tom,

                            I have checked those points a zillion times, and find all of the things you've suggested to be right.

                            Thank you again,
                            efs

                            Comment


                              #29
                              RE: parent records only

                              Ed,

                              You might want to try to rebuild the index for both tables. Also make sure that the the "po_num" field is the same length in both tables (i.e. char:8 | char:8)

                              Comment


                                #30
                                RE: parent records only

                                Hi Ed,

                                See if this works; put a filter on the form on which the embedded browse is located and it will filter the embedded browse.

                                If you can't get it to work, can you post a zip file so that we can see exactly what the problem is as Tom suggested? Or, perhaps you may have sent a zip file to him via email.

                                If you are able to do this, I am confident your problem can be solved.

                                kenn
                                TYVM :) kenn

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

                                Comment

                                Working...
                                X