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



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

Ensure form is open

  • Filter
  • Time
  • Show
Clear All
new posts

  • Ensure form is open

    I have a master form which I open and set the global variable "selptID" based on a field in the form. If the user presses a button, a new form based on a table which is linked by ptID field to the master table (which is what the original form was based on) is opened.

    I then set the child table key "ptID" to the global variable. I did not try to use a set to handle the copying of the key to the child table because I had had problems doing that in the past, so I set it programatically.

    I set the script to set the child key value in the child form's OnInit event. The problem is, if someone opens the child form without the parent being open, the key will get set to whatever value is in the global variable at the time.

    I would like to check to make sure the parent form is open before allowing any changes to the child key. That way, the currently opened parent key gets promulgated to the child. Is there a way to check for this?

    I'm sure someone has a better way to do this, such as using sets and I am open for suggestions.

    Thank you!
    David A. Volgas, MD

  • #2
    Re: Ensure form is open

    is_object() can be used to determine if a form is already open.


    • #3
      Re: Ensure form is open

      Thanks! Is there a better way to make sure that the child form has the same key as the parent? Sets seem to get confused when they are complicated.
      David A. Volgas, MD


      • #4
        Re: Ensure form is open

        I think your design should guarantee that the only way the child form can be seen by the end user is by running a script from the master form. Separate scripts should be used to open the child form for a new record and for edits to an existing record. Navigation in the called form should be suppressed. lock it down tight. User works on one record then either saves edits or cancels edits. No queries, no finds, no toggles to browses. Locked down tight. This was much easier before Windows made things so flexible.

        Alternatively, do your data entry using completely scripted xdialogs.


        • #5
          Re: Ensure form is open

          As always, you are a huge help. Thank you!

          Does changing the script to the "OnEnter" event help?

          David A. Volgas, MD


          • #6
            Re: Ensure form is open

            David, my preference with opening a child form that is being used to enter a related record is to use a button push on the calling form. The OnPush event script loads the called form but keeps it hidden. The script then begins the new record in the hidden form. The script then assigns the link field value to the foreign key field in the new record. This can be done by assigning the field value to the value property of the object in the called form that displays the link field value. That field can then be made readonly by the same script. Finally, the script shows the form to the user.

            On occasion my script will commit the newly begun record before showing the form to the user. This is handy when the called form involves a memo field, or when I need to commit an autoinc field value. The user then finishes the "new" record in change mode instead of enter mode.


            • #7
              Re: Ensure form is open

              Thank you. Maybe if I keep at this long enough, I will get good at design. It's not really explained well, but I think I remember in the DOS version, that "Enter" mode is only used for new records, rigtht? It's equivalent to setting the record cursor to the next record past the end of the file.

              David A. Volgas, MD


              • #8
                Re: Ensure form is open

                "ENTER" mode is simply a descriptor. Used to tell us what's going on in the form at any point. Parentform.mode_get() will return it. Use this to create a new calc field in one of your forms and watch it change as you enter or edit some records. the most common "modes" are VIEW, ENTER, CHANGE. You'll understand this better if you play with the calc field a bit.

                Your idea of using the OnSave event to run your script may or may not be a good idea. This event fires when the form saves a record, so it will run the script whether the record just saved is new or even if the user is simply editing a field value. You probably don't want the same script to run in both cases, if you see what I mean.


                • #9
                  Re: Ensure form is open

                  I'm not using OnSave for anything, except on one form, to recalculate some fairly complicated scores. I put the script setting the key value iin the OnEnter event. That way, it should only fire when I have a new record on the screen.

                  David A. Volgas, MD