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
Devcon 2020 Goes Virtual! LEARN MORE >

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

Action scripting for new record in Child Database

Collapse
X
Collapse
 
  • Page of 3
  • Filter
  • Time
  • Show
Clear All
new posts
Previous 1 2 3 template Next
    #31
    RE: Action scripting for new record in Child Datab

    Zoom to form only works if the record has been written to the database and the line in the embedded browse has focus.

    If you create a new record in the embedded browse and then zoom to form you will open the form with the previouse record in the browse.

    I have found a roundabout solution but not satisfactory.

    Set the row doubleclick on the embedded browse to 1. Set a value in an indicator field. (If you save a record and there have been no changes the record is not saved unless at least one field in the record has been changed. The indicator field must be on the main form or a tab as a visible or hidden field, since you can only set values for items on the current form). 2. Save the record. 3. Zoom to child form.

    This requires that a user click on in the embedded browse, and then double-click on the new record line to open the form.

    I still think we need a simple action scripting option to create new child record and specify entry form format to use.

    Comment

      #32
      RE: Action scripting for new record in Child Datab

      Michael,

      Here's a working example, composed completely in action scripting sequences.

      Unzip the attachment to a separate folder. Do not mix it with your development work.

      When you open the database you'll find the simplest of arrangements. Two tables, Customers and Phones. One set, with Customers primary and Phones as child. The design enables you to store as many different phone numbers for each customer as you might want to, cause the link in the set is 1:N. Anyway, begin with the Primary form. You'll see the embedded browse is read only. No new child records can be entered through it. There's a single button on the form, which is where you should focus your study. It opens a second form based on the Phones table, and begins a new record. Notice that when this happens the link field value necessary to maintain the relationship between the new Phones record and the current Customer record is supplied automatically.

      Have fun tearing it apart.

      -- tom

      Comment

        #33
        RE: Action scripting for new record in Child Datab

        Just put a button "new record" outside of the embedded browse. Have this open a copy of the form used as the zoom to form. The only difference would be that the zoom version has buttons for change, cancel, save, close. The new version also needs a "new record" button. Works like a charm and I use it all the time.

        Russ

        Comment

          #34
          RE: Action scripting for new record in Child Datab

          Just a note. You can only create or edit this script if the child form is open while in the desigh mode for the customer form.

          Your script works and is a possible solution, but it still shows that a single action scripting function to create a new child record using a designated form is required.

          The average new user will never deduce this type of script.

          My target audience at this moment is the group president and senior vice presidents in a major corporation who have realised the futility of spreadsheets for maintaining management information needs. They will want to tweak and modify the applications themselves on occasions. The solutions must be flexible to create, and require little programming or database experience to provide solutions. Alpha 5 can provide this. This is the only stumbling block so far.

          Comment

            #35
            RE: Action scripting for new record in Child Datab

            Do you really want those people "tweaking" your application? I think you might be asking for trouble.

            Russ

            Comment

              #36
              RE: Action scripting for new record in Child Datab

              This might get Alpha 5 to be the database of choice instead of Access in a corporation with over 100,00 employees. The application is to be used only by senior management and the data in it could be very sensitive. They will want total control. Alpha 5 simplicty of use and encryption option are major factors.

              Comment

                #37
                RE: Action scripting for new record in Child Datab

                Michael,

                One man's requirments are another's options, especially on matters of interface or style. I'm certain the designers at Alpha spent many hours thinking about the level of 'granularity' they thought best met the user's needs.

                I'm glad you liked my script, since it seemed to meet your requirements. If you needed to demonstrate this level of functionality without using any coding, I trust you found it helpful.

                If you feel strongly about the utility of a one-step approach, I believe you could build your own 'new record function' or 'xdialog' to supply the desired interface for your folks. This could be compiled into the AEX and would be available to everyone using the database as an addin.

                -- tom

                Comment

                  #38
                  RE: Action scripting for new record in Child Datab

                  I agree with Michael that this could be improved. In fact, after selecting the form and then arriving at the last part of the genie (Show which records in the Target Form or Browse), the ability to choose an 'Enter New Record' option would be a real value. It would be a natural fit.

                  That would make this a one step procedure; create a button to open the form, select the form and then enter a new record option. More than that, it would make it so that a person with no experience, could follow the yellow brick road and not get lost.

                  kenn
                  TYVM :) kenn

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

                  Comment

                    #39
                    RE: Action scripting for new record in Child Datab

                    Ken,

                    Perhaps so. You'd be combining 3 or 4 logical steps into a single step with 3 or 4 settings or options. For me, this is an interface issue. If the interface becomes easier to use for a greater number of people, so much the better. -- tom

                    Comment

                      #40
                      RE: Action scripting for new record in Child Datab

                      Ken, Michael,

                      A bit of further investigation reveals that the number of steps used in my earlier example can be easily reduced. There's no need to 'get' the value of the link field to store it in a variable simply to pass it to a field in the new record on the second form. Action scripting permits you to simply pass the value of the link field directly. There's no need to store it in a variable in a separate action step.

                      What the revised script boils down to is:

                      1) Open the new form
                      2) Begin a new record there
                      3) Pass the link field value to the key field in the new record

                      -- tom

                      Comment

                        #41
                        RE: Action scripting for new record in Child Datab

                        Hi Tom,

                        While it's a 3 step process, it's not a process that is easily decipherable by an inexperienced user. Neither Michael or I are inexperienced users but both of us had difficulty. Yes, I think both of us could see that the linking value needed to be passed but it how to do it wasn't easily discernable.

                        It appears to me that if a form is opened as in a case such as this, step 3 should be an automatic part of step 1. There is an option to open a form to show a record in the child table that matches a parent value so there could be an option to open the form in new record mode as well. Perhaps Alpha will give us that option.

                        kenn
                        TYVM :) kenn

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

                        Comment

                        Previous 1 2 3 template Next
                        Working...
                        X