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

Automatic Advance using a Set Form

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

  • Automatic Advance using a Set Form

    After creating a Set using the 1:Many Format and modifying the Default Form to accommodate the Parent and 13 Child Files, I began testing the data entry.

    The Parent File includes the Participant Information, and each Child File is a specific subtest of a Memory Test that we are standardizing. The linking field for each file is the ID# of the Participant.

    During data entry, the cursor will advance from field to field within a Participant and Child File, but will not automatically advance from one File to the next, nor will the Set Form advance to a blank form once the data has been entered for a Set Form. This means that the cursor manually has to be placed at the beginning of each child file at the completion of the previous file entry, and that at the completion of the set entry the form has to be closed and reopened in order to enter the next Set Form data.

    Is there better way to handle data entry for a set? I am not able to use the autoincrement feature for ID# as it is an assigned number by the administrator.

  • #2
    RE: Automatic Advance using a Set Form

    Jean,

    By 'file' I presume you mean 'record' as each client name in your database is referred to as a record. There are a couple of things you can do.

    1. Place a button on the form to create a new record. Also add a button to cancel the entry and you migh want a button to save the entry.
    2. When you get to the end of the tab order, you can place a bit of code on the field's CanDepart or OnDepart event which will cause a new record to open. (You can steel the code from the code on the new record button) You migh also want the Cancel button to cancel and entery if necesary.

    Others may have more ideas but start simple, use the 3 buttons as that makes things clear and easy for the user.

    kenn
    TYVM :) kenn

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

    Comment


    • #3
      RE: Automatic Advance using a Set Form

      Jean, your basic design may prove troublesome. I try to avoid sets with more than 3 members, though there are exceptions. Are all your child tables linked one to many, back to the primary table?

      You might benefit from reading Dr. Wayne's article, 'Simplifying your Application', at www.learn alpha.com.

      -- tom

      Comment


      • #4
        RE: Automatic Advance using a Set Form

        Yes, all the Child Files are linked back to the Parent File using the ID as a link.

        Thank you for recommending the suggested article. I will check it out.

        Comment


        • #5
          RE: Automatic Advance using a Set Form

          I was under the impression that each Record entered on a SET Form was the combination of the Participant file and all of the child files which are linked by ID#. Is this inaccurate?

          I will attempt to apply buttons as you suggest. I'll let you know how it works out.

          Thanks so much for your suggestions.

          Comment


          • #6
            RE: Automatic Advance using a Set Form

            Jean,

            The terminology is tricky but here's what I understand is at work when you use a form based on a set.

            The tables that comprise the set are opened automatically when the form opens. A 'composite' record is created in the record-buffer which contains the values from the fields in the current record in the primary (parent) table, and the values from the current record in each linked child table. However, edits are saved to each table separately. It's possible, for example, to use sucha form and save a new parent table record without simultaneously creating a new (and blank) child table record in each of your child tables. Likewise, it's possible to add child table records to a single child table, without creating new records in the parent or in the other children.

            -- tom

            Comment


            • #7
              RE: Automatic Advance using a Set Form

              After creating a Set using the 1:Many Format and modifying the Default Form to accommodate the Parent and 13 Child Files, I began testing the data entry.

              The Parent File includes the Participant Information, and each Child File is a specific subtest of a Memory Test that we are standardizing. The linking field for each file is the ID# of the Participant
              -----------------------------------------------

              I would think that anyone who could navigate this form, and know which subtest they're current viewing........would have a memory exceeding a pachyderm.

              Comment


              • #8
                RE: Automatic Advance using a Set Form

                You are absolutely right. I have been doing some trial and error entry to see just what happens when I enter a set. It seems to me that other than giving the data entry person the ability to have all forms on one screen, there really isn't any benefit to entering the data on a set form. (Although, this is a pretty big benefit when you are talking about consolidating 14 forms onto one screen.)

                I have experimented with adding buttons to forms, but I don't see how this helps me with a Set Form as only the Parent Form is displayed in "Form Mode" and all the child forms and fields are displayed in "Browse Mode". It doesn't appear that buttons appear in a "Browse" setting. Is this correct? What I am attempting to do is to force the data entry sequence to go from the last field on one child form to the first field on the next child form until all the "children" are complete and then progress to the next "Parent" and its associated "Children."

                Any suggestions?

                Comment


                • #9
                  RE: Automatic Advance using a Set Form

                  Actually, it's not the navigation that is the problem. Each field is labeled with the subset that it represents, so there is little problem with knowing what subset you are in. The problem lies in getting the Set Form to be user friendly.

                  Comment


                  • #10
                    RE: Automatic Advance using a Set Form

                    Hi,

                    >>What I am attempting to do is to force the data entry sequence to go from the last field on one child form to the first field on the next child form until all the "children" are complete and then progress to the next "Parent" and its associated "Children."

                    It seems to me that if you have one to many relationships that what you want is difficult, because you may want to create more child records, so how would the form "know" when to create a new parent record?

                    Regards,

                    Jay Talbott
                    Jay Talbott
                    Lexington, KY

                    Comment


                    • #11
                      RE: Automatic Advance using a Set Form

                      Perhaps you could use a single browse (or a single sub-form) for all the child records which would contain a field identifying the sub-test. A button on the form could query the next sub-test for the participant to begin entering data. If this sounds too complicated, you may find help with your form here on the board.

                      Comment


                      • #12
                        RE: Automatic Advance using a Set Form

                        Jean,

                        Here's what I've done. Others do it similar or differently.

                        I have a set with a 1:Many table and 5 1:1 tables. The form is based on the set. On the form I have a few fields from the parent table and then put a tabbed object on the form. Each tab represents a table. On some of the tabs, I have a browse based on a child table but not the child table as it's linked to the set, just on the child table alone. I also have a subform on one of the tabs that's also built on a child table alone. This works very well for me and it may be something you would like to try.

                        However, I beleive there's a difference in 'overhead' when 4-5 child tables on a 1:1, are opened at the same time (as in a set) vs the same number of open child tables on a 1:Many relationship. I wouldn't do that.

                        There's so much flexibility in A5 that you could have a browse on your form and whe you double click on a record or a person's name, it takes you to another set or to a table which is not part of the set and enter/edit data, which as I think about it, may well be a better method than what I've got setup. (Whatcha don't think of when trying to help someone.) Anyhow, if this method is utilized, variables are used to pass values from the parent form to the unrelated table

                        Gotta admit that this type of power in A5 is mind boggling compared to what I have to do when using Access since Access doesn't have anywhere's near this flexibility w/o extensivly learning VB.

                        No doubt, there are some who will disagree with this, all or in part. But, this database will not have tens of thousands of records either. Hope this gives you some ideas.

                        kenn
                        TYVM :) kenn

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

                        Comment


                        • #13
                          RE: Automatic Advance using a Set Form

                          HI Jean,

                          I use a composite form with the parent at the top and an embedded
                          browse at the bottom of the child table. In the onkey event for the form I have the following script:

                          if a_user.key.value = "{F3}"
                          a_user.key.handled=.t.
                          IF a_user.key.event = "down"
                          f=parentform.active()
                          if f="browse1"
                          parentform:numstore.activate()
                          parentform.fetch_next()
                          else
                          Browse1.Activate()
                          browse1.new_record()
                          ' browse1:firs_nam.activate()
                          sys_send_keys("{Enter}{enter}{enter}{enter}")
                          browse1:percent.activate()
                          end if
                          end if
                          end if

                          When the form is initiated, the focus is on the parentso pressing F3
                          places the focus on the first field of a blank record to add to
                          existing child records for that parent record. When i have entered all
                          necessary data in the child record, pressinf F3 advances to the next
                          parent record and the focus again is on the first blank record of the
                          child table. Consequently the previous data entered into the child
                          is saved. BTW, you can delete the sys_send_keys line. You will also have to modify the field names to suit your application.

                          efs

                          Comment


                          • #14
                            RE: Automatic Advance using a Set Form

                            Jean,

                            There are a lot of good suggestions here for making things "more perfecter" but, assuming you are using browse tables for the child tables, maybe this is all you will need...

                            Try the F6 key. This will move you from "region" to "region" (I think the term is a carryover from A4) which seems to mean the same as "browse" to "browse". This isn't perfect but it's better than switching from the keyboard to the mouse and back again.

                            I've used this method a number of times but can't remember the details. I know it will move you out of the current browse to the next form object in tab order - which could be another browse, or a button, or a field in the parent form. I'm just not sure if you can move into a region from the parent form this way - but that may not be important because I think you can move to the first browse just by setting the tab order.

                            Comment


                            • #15
                              RE: Automatic Advance using a Set Form

                              I would use this approach - when the user enters a new parent, the client, and reaches the last item in the tab order for the parent - you could put this code at the candepart event for that field -

                              response=ui_msg_box("Ready for the first child? ",4)
                              if response=6 'answered yes
                              parentform.commit()
                              form.view("child1form")
                              end
                              end if

                              'this would take you to the first logical child form

                              'then at the onactivate event for the form itself
                              'when they conme back from the first child

                              'put something like this:

                              check:
                              tbl=table.get("childonename") 'if they didn't enter from before

                              if tbl.custid=parentform:custid.value
                              'do nothing - they have one record for the 1st child
                              else
                              response=ui_msg_box("Ready for the first child? ",4)
                              if response=6 'answered yes
                              form.view("child1form")
                              end 'stop the script from running here
                              end if

                              tbl=table.get("child2name")
                              if child2.custid=parentform:custid.value
                              'do nothing
                              else
                              response=ui_msg_box("Ready for the 2nd child? ",4)
                              if response=6 'answered yes
                              form.view("child2form")
                              end 'stop the script from running here
                              end if
                              ad infinitum

                              you will have to play with this, but it should give you the core of my idea - every time you activate the form, it would systematically check each child for a record - and if there was none, ask if you want to enter one.



                              Cole Custom Programming - Terrell, Texas
                              972 524 8714
                              [email protected]

                              ____________________
                              "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

                              Comment

                              Working...
                              X