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

Refresh display and refresh objects - I thought I knew what they did

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

    #16
    Re: Refresh display and refresh objects - I thought I knew what they did

    Originally posted by Tom Cone Jr View Post
    Jeff the msg board works better as a knowledge base if we all resist turning a single thread into a blog. Please try to limit each thread to a single question or topic. Thanks.
    Tom, sorry you saw it this way. I saw it as related to the question, and if you look earlier in the thread, this is how I began the thread -- it was all related. But I understand you POV.

    Jeff

    Comment


      #17
      Re: Refresh display and refresh objects - I thought I knew what they did

      Jeff, no apologies needed.

      Ray, from my vantage point it seemed the topic of this thread was the "refresh display" method of a desktop form. Now it seems Jeff asking about ways to change field values in a single parent table record when child table values are entered or changed in any of several possible child table records. These are two very different things, or so it seems to me. For what it's worth I think my suggestions in the "original" thread remain valid. (See post #4 in that thread.)
      Last edited by Tom Cone Jr; 07-04-2013, 09:35 AM.

      Comment


        #18
        Re: Refresh display and refresh objects - I thought I knew what they did

        Jeff,

        Check this screencast.

        Comment


          #19
          Re: Refresh display and refresh objects - I thought I knew what they did

          Originally posted by Tom Cone Jr View Post
          Jeff, no apologies needed.

          Ray, from my vantage point it seemed the topic of this thread was the "refresh display" method of a desktop form. Now it seems Jeff asking about ways to change field values in a single parent table record when child table values are entered or changed in any of several possible child table records. These are two very different things, or so it seems to me. For what it's worth I think my suggestions in the "original" thread remain valid. (See post #4 in that thread.)
          Tom, at the risk of beating a dead horse, I now see that I first started a thread related to sensing changes in the child at the parent level, to which you responded. From discussions you and I had, it transitioned to my need to change calculated fields in the parent to user-entered fields in order to update these field values under script control, especially when the script was executing from the child to affect the change in the parent. It was in setting up the OnSave script to change the values in the parent that I discovered that the refresh display feature was not working as I expected. This led to my starting this thread, though it was related to my real objective to sense changes in the parent from the child. My question to Stan, who provided a solution to the refresh display, was simply under the assumption that maybe he also had experience with the child to parent updates.

          I will be mindful in the future that these apparent topic switches in a thread should be handled as a separate thread.

          Thank you.

          Jeff

          Comment


            #20
            Re: Refresh display and refresh objects - I thought I knew what they did

            You don't happen to have a way to sense a change in the parent table when a change is made in the child, do you?
            There is no sensing going on, it is all event driven.

            You can code various table and field level events in a table's field rules.
            There can be only one.

            Comment


              #21
              Re: Refresh display and refresh objects - I thought I knew what they did

              Originally posted by Stan Mathews View Post
              There is no sensing going on, it is all event driven.

              You can code various table and field level events in a table's field rules.
              I'm just using the term "sensing" to refer to the result of a procedure to affect an outcome in the parent from an action in the child. I know that table or form events in the child will be used, and I'm sure it's easier done than said. I just wondered if you had experience with it since, like so many things, there are various ways to achieve the desired outcome and sometimes, after playing with it, you settle on one that has advantages.

              Jeff

              Comment

              Working...
              X